Websphere Integration Developer 6.1 Tutorials: Versioning

Versioning How to

How to use Versioning

Related links	Versioning Creating versions of your process to be used with SCA components and exports Late binding using a partner link extension Creating a version of your state machine Creating a version of your human task Creating a version of your process
Why use versioning?
Wired References When you wire a module to another module, the calling module (wire from) will be statically bound to the called module (wire to). Thus, the calling module will always call exactly the same module all the time.
Create an Unwired Reference To enable the ability of a calling module to call a different module without making any changes to the calling module, do not wire the calling module to any target component (SCA or import component). To create an unwired reference, proceed as follows: Right-click on the component (i.e HandleClaimProcess) and select Add > Reference. In the Add Reference window, select the reference you want to add (i.e ApprovalProcessIF) and click OK. For unwired references, the binding will be dynamically selected during runtime.
An Unwired Reference This is an example of an unwired reference. Notice that unwired references causes warning CWSCA8015W to appear.
Set the Process Template In the business process editor, Click the reference that you want to call (ApprovalProcessIF) Click Properties/Description for ApprovalProcessIF and enter ApprovalProcess in the Process Template: field.
ApprovalProcess ApprovalProcess is the name of the process called by the caller (HandleClaimProcess). There are 3 versions of ApprovalProcess stored in different modules (.....V1, ....V2, and ....V3).
Which process to call? How does a calling module (i.e HandleClaimProcess) determine which sub-process to call (i.e ApprovalProcess v1, v2 or v3)? It doesn't. The runtime system determine which process to run base on the Valid From settings. The different versions of ApprovalProcess must have different Valid from settings.