Migration Reference

• Change the type of the abstract component to a valid component and implement as appropriate.

• Abstract component
• Wires between .NET components are not migrated and the corresponding component services and references are not migrated to the abstract component.

• Change the type of the abstract component to a valid component and implement as appropriate.
• Recreate missing component services, references, and wires.

• @Service annotation generated for a Java component with Out-* MEP.
• @Reference annotation for an Out-* reference:

  @Reference
  OutInPT referenceName1 = new 
   org.example.www.outin.OutInPT(){
    public OutInOperationDocument
    outInOperation(
     OutInOperationResponseDocument 
     parameters){
    //..
   }
  };
  

• If you want to be able to regenerate the component implementation, convert the 2.x class structure to the 3.x class structure following the procedure in the appendix Converting Migrated Java Component Implementations of Java Component Development .
• Update the package names of SOAPException and SOAPDetail to com.tibco.amf.platform.runtime.

  extension.exception.

• Update the package names of EndpointReference, and ReferenceParameters to com.tibco.amf.platform.runtime.

  extension.exception.

• Update the package names of WsAddressingConstants to com.tibco.amf.spline.api.constants.

  WsAddressingConstants.

• Extract header properties from com.tibco.amf.platform.runtime.extension.

  context.MutableRequestContext instead of HashMap.

• Extract WS-Addressing properties from com.tibco.amf.platform.runtime.extension.

  context.MutableRequestContext instead of HashMap.

• If you use the class org.osoa.sca.ComponentContext, open the Java plug-in manifest in the manifest editor, go to Dependencies tab and add the import package: org.osoa.sca.

• Context Mechanism In 3.x the context parameters are defined on the component/composite/implementation service & reference.

  Context Parameters - Context parameters defined as a simple type in 2.x are migrated as context properties with the same direction and of type that is the Java equivalent of the 2.x schema type. Parameters defined at the output level are copied to the fault level after migration.

  Transport and Security context - Transport context properties are migrated as context parameters of type bag. The HTTP headers are migrated as HttpHeader of type bag. The JMS properties are separated during migration into JmsHeaders and JmsProperties. Security context is migrated as a mediation parameter of type security.

• Set Context Task Mapping of 2.x context parameters is retained and mapped accurately.
• Set Dynamic Reference Task The Set Dynamic Task Endpoint Reference mechanism was changed from 2.x to 3.x by using Application Name & Service Name (3.x) instead of Service Name & Service Namespace (2.x). The Set Dynamic Reference task uses a mapper to set these values. The migration attempts to preserve these mappings even though the semantics of the dynamic routing have changed.
• End Task The value of the End Type property has changed from error to Stop Message Delivery and now mandates the configuration of a ’At-least-once’ policy at the mediation operation level.
• Query Database Task Shared resources profile references defined in the Query Database task are migrated as property references.
• Timeout Faults Mediation Flows 3.x contain a timeout fault path for all target operations. Mediation Flows 2.x do not contain this fault path which is automatically added during migration.

• Update these mappings to match their 3.x environment as it relates to dynamic endpoint references.
• Add the correct policy.

• 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.

• Promoted service with SOAP binding
• JMS Connection Factory, JMS Connection Factory Configuration, JMS Destination, JNDI Connection Configuration

• Promoted reference with SOAP binding
• If the binding pointed to an HTTP Client Shared Resource, an HTTP Client.

• Promoted reference with SOAP binding
• JMS Connection Factory, JMS Destination (inbound), JMS Destination (outbound), JNDI Connection Configuration

• Convert reference to a supported binding type.

• 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.

• 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.

• 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.

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.

See TIBCO ActiveMatrix Binding Type for TIBCO Adapters Binding Development.

See TIBCO ActiveMatrix Binding Type for EJ6 Binding Development.

• 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 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.