WCC ECLI JIL Import Fails after Upgrading WAAE to 11.3.6 SP6 on AIX

Document ID : KB000007535
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

After upgrading an AIX WAAE server to 11.3.6 SP6, which includes an updated Command Sponsor, WCC ECLI JIL imports begin to fail with a "Command processing exception encountered" error. All other ECLI commands, including the JIL export function, continue to work properly after the upgrade.

NOTE: This problem only occurs in environments where the Command Sponsor is running on AIX.

 

 

Resolution:
On the AIX server where the Command Sponsor is located, perform the following steps: 

1. cd $IGW_LOC

2. Run './S99igateway stop'

3. Edit the igateway.conf file and look for this section...

<JVMSettings>
     <loadjvm>true</loadjvm>
     <javahome>/opt/CA/SharedComponents/iTechnology/jre_cs</javahome>
     <!-- <Properties name="prop-1">
          <system-properties></system-properties>
     </Properties> -->
</JVMSettings>

Modify this section so that it contains the following changes highlighted in red...

<JVMSettings>
     <loadjvm>true</loadjvm>
     <javahome>/opt/CA/SharedComponents/iTechnology/jre_cs</javahome>
     <!-- <Properties name="prop-1">
           <system-properties></system-properties>
     </Properties> -->
     <Properties name="cs.ext.dirs">
          <system-properties>java.ext.dirs=/opt/CA/SharedComponents/iTechnology/jre_cs/lib/ext</system-properties>
     </Properties>
</JVMSettings>

If you are not using the default SharedComponents install location on this machine (/opt/CA/SharedComponents), make sure the path in the change above is correct for your environment.

4. run './S99igateway start'

NOTE: If the environment is HA where you have another Command Sponsor on your secondary server, you will need to perform these steps on that server as well.