XML File not changed when transporting RA Web Service Objects using transport case

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

Error Message :
org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: Unexpected subelement s_change_id
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at WS_1476865545989.Ws_ComputerStub.fromOM(Ws_ComputerStub.java:815)
at WS_1476865545989.Ws_ComputerStub.createVm(Ws_ComputerStub.java:143)

When transporting RA Objects (in this case Web Services) with the transport case an Error may arise.

The following error message is seen when the job runs.

Agent Log:

org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: Unexpected subelement s_change_id
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at WS_1476865545989.Ws_ComputerStub.fromOM(Ws_ComputerStub.java:815)
at WS_1476865545989.Ws_ComputerStub.createVm(Ws_ComputerStub.java:143)

This happens when the Web Service Job is transferred via a Transport case using the same connection object with different endpoints.

Investigation

The problem can be seen in the example below after exporting the JOB from the DEV environment the export contains the service URL (../serverkonfigDev).

DEV Screenshot:

<Please see attached file for image>

Opening the Job in the PROD environment shows the correct URL (without DEV) but when requesting the old URL seems to be used.

PROD Screenshot:

<Please see attached file for image>

Using the "Reload" function in the object is not an option because the WSjar files are copied to every Client and are not centrally located.

 

Environment

OS Version: N/A

Cause

Cause type:
By design
Root Cause: The RA Web Service Solution v3 uses an adapter file that causes the issue. In v4, no adapter file is needed so this is not an issue.

Resolution

Update to a fix version listed below or a newer version if available where no adapter file is created.

Transporting Web Service jobs and modifying parameters will not work. The point is, that some  information such as the URL and operation are embedded in the Adapter Jar file which is created during the creation of the connection. This means that just overwriting or changing the attribute will not help.

 

Fix Status: Released

Fix Version(s):
RA Web Service SOAP Solution 4.0.0 - Available

Additional Information

Workaround :
Change the exported XML from:

<component con="0" enc="0" type="2" value="https://XXX.XXX.XXX.XXX/serverkonfigDev/" xmlName="connectionUrlField"/>

to

<component con="0" enc="0" type="2" value="https://XXX.XXX.XXX.XXX/serverkonfig/" xmlName="connectionUrlField"/>

Or if possible use the 'Reload' function in the Object if the files are not copied to every Client and are centrally located.