Migration Reference

Depending on your input object, you might have different migration output elements and different required actions.

Project and Component Migration
Input Object Migration Output Required Actions
SOA Project Composites, Shared Resources, and Deployment Packages migrated to the correct special folder type, but folders are not renamed. None.
Topic Abstract component
  • Change the type of the abstract component to a valid component and implement as appropriate.
Service and Reference Migration
Input Object Migration Output Required Actions
SOAP/HTTP Service
  • Promoted service with SOAP binding
  • If transport type is HTTPS, transport type is HTTP
  • Connector Name property set to resource profile name or to httpConnector.
  • If Enable WS-Addressing and Anonymous checked in binding, the binding is configured with policy set "WSAddressingPolicyForService_BindingName
  • If Enable WS-Reliable Messaging checked in binding, the binding is configured with policy set "WSRMPolicy_BindingName
  • Create an HTTP Connector and install instance on node prior to deployment.
  • If transport type was HTTPS, configure HTTP Connector for SSL.
.
SOAP/JMS Service
  • Promoted service with SOAP binding
  • JMS Connection Factory, JMS Connection Factory Configuration, JMS Destination, JNDI Connection Configuration
None.
SOAP/HTTP Reference
  • Promoted reference with SOAP binding
  • If the binding pointed to an HTTP Client Shared Resource, an HTTP Client.
None.
SOAP/JMS Reference
  • Promoted reference with SOAP binding
  • JMS Connection Factory, JMS Destination (inbound), JMS Destination (outbound), JNDI Connection Configuration
None.
SOAP Reference with Third-Party Binding The project will migrate but will result in a composite that is not supported.
  • Convert reference to a supported binding type.
AMX Service
  • Promoted service with Virtualization binding.
  • If a port type was set on the service then the name for the generated Virtualization binding will match the name of the port type. Otherwise, the name of the Virtualization binding will be Virtualization.
None.
AMX Reference
  • Promoted reference with Virtualization binding.
  • If a port type was set on the reference then the name for the generated Virtualization binding will match the name of the port type. Otherwise, the name of the Virtualization binding will be Virtualization.
  • Wire the applications at deploy time using Administrator or create a wrapping composite with components of type composite wired together.
JMS Service
  • Promoted service with JMS binding
  • JMS Connection Factory Configuration
  • JMS Connection Factory
  • JMS Destination Configuration
  • JMS Destination
  • JNDI Connection Configuration
  • JMS target address is mapped to JMS Destination Configuration
  • JMS reply address is mapped to JMS Destination
  • Configure generated JMS resource templates to point to JNDI Connection Configuration.
JMS Reference

Promoted reference with JMS binding

  • Promoted service with JMS binding
  • JMS Connection Factory Configuration
  • JMS Connection Factory
  • JMS Destination Configuration
  • JMS Destination
  • JNDI Connection Configuration
  • JMS target address is mapped to JMS Destination Configuration
  • JMS reply address is mapped to JMS Destination
  • Configure generated JMS resource templates to point to JNDI Connection Configuration.
Shared Resource Migration
Input Object Migration Output Required Actions
JMS Shared Resource
  • JMS Connection Factory
  • JMS Connection Factory Configuration
  • If connection type is JNDI, a JNDI Connection Configuration
  • If connection type is direct, create a JNDI Connection Configuration.
  • Configure generated JMS resource templates to point to JNDI Connection Configuration.
JNDI Shared Resource
  • JNDI Connection Configuration
  • If the resource contained an identity, an Identity Provider and an empty Keystore Provider.
  • Rename resource template if shared resource name contained a space.
  • Configure the Keystore Provider.