In this blog post, we are going to discuss about the SOA composite application revisions. Whenever, we deploy a composite application a revision is required during the deployment. And the WSDL (web service definition language) URL can be accessed with the composite name followed by the revision number.
So let`s start with the deployment of our first application: The application which we are going to deploy is the Account Status application which we have developed in our previous tutorials.
Here from the screen shot you can see that we have not yet deployed any composites to the SOA servers.
Let`s deploy one using Jdeveloper:
Next screen is the Composite Deployment Action, Select the Deploy to Application Server option in Jdeveloper, then click NEXT.
On the deployment Configuration Screen. Select New Revision ID to 1.01 and Mark composite revision as default, then Click NEXT.
Select Domain as SOA domain or configure SOA domain then select and Click NEXT. On the next screen, select the target SOA server and corresponding partitions for which you want to deploy the achieve then Click NEXT.
On the next screen, Click FINISH.
From the console output; You can see the deployment logs:
[11:25:03 AM] ---- Deployment started. ---- [11:25:03 AM] Target platform is (Weblogic 10.3). [11:25:03 AM] Running dependency analysis... [11:25:03 AM] Building... [11:25:15 AM] Deploying profile... [11:25:15 AM] Updating revision id for the SOA Project 'AccountStatus.jpr' to '1.01'.. [11:25:15 AM] Wrote Archive Module to C:\SOADevelopment\AccountInfo\AccountStatus\deploy\sca_AccountStatus_rev1.01.jar [11:25:15 AM] Deploying sca_AccountStatus_rev1.01.jar to partition "default" on server AdminServer [<a href="http://192.168.1.9:7001">http://192.168.1.9:7001</a>] [11:25:15 AM] Processing sar=/C:/SOADevelopment/AccountInfo/AccountStatus/deploy/sca_AccountStatus_rev1.01.jar [11:25:15 AM] Adding sar file - C:\SOADevelopment\AccountInfo\AccountStatus\deploy\sca_AccountStatus_rev1.01.jar [11:25:15 AM] Preparing to send HTTP request for deployment [11:25:15 AM] Creating HTTP connection to host:192.168.1.9, port:7001 [11:25:15 AM] Sending internal deployment descriptor [11:25:15 AM] Sending archive - sca_AccountStatus_rev1.01.jar [11:25:20 AM] Received HTTP response from the server, response code=200 [11:25:20 AM] Successfully deployed archive sca_AccountStatus_rev1.01.jar to partition "default" on server AdminServer [<a href="http://192.168.1.9:7001">http://192.168.1.9:7001</a>] [11:25:20 AM] Elapsed time for deployment: 17 seconds [11:25:20 AM] ---- Deployment finished. ----
Also login to the em console : http://host/port/em and you will see the composite deployed in the em console:
Now, let`s follow the above instructions and redeployed Account Status SOA Composite Application to the same SOA server using Jdeveloper. However, this time I have change the revision version to 1.02 and set this version [1.02] to the default version. You can see from the below screen shot that both the versions are deployed successfully.
Now, if you will try to access the wsdl using the following url:
You will get to the newest default version [1.02].
But if you see that, we still have the older version deployed. So how can we access it?
To access the older version we need to access it using the following url: Where we need to specify the version number.
Now, as we have deployed the second application with the new version [1.02]. The application [1.02] is our default application. Now, due to some reason If we want our original application (version [1.01] to be the default or primary SOA application how can we change it during the runtime?
So to change the application version to default. Login to the em console http://host:port/em.
Under Farm_domain –> Expand SOA –> Expand soa-infra –> Expand default –> Select the application which you want to set as a default application, in our case it is : AccountStatus [1.01].
Then click set as default as shown in the screenshot below: