Skip to content

Installation within Integration Server

Jump to bottom
Richard Tomlinson edited this page Jul 8, 2017 · 26 revisions

Installation of the server libraries

Installation requires the placing of three jar files into the IS lib/jars directory:

  • For 9.0 place them in SoftwareAG/IntegrationServer/lib/jars
  • For 9.5 onwards, place them in the lib/jars of the instance e.g SoftwareAG/IntegrationServer/instances/default/lib/jars

The jar files required are

Edit the file SoftwareAG/IntegrationServer/config/invokemanager.cnf (For 9.5 and onwards, again edit in the instance directory, e.g. SoftwareAG/IntegrationServer/instances/default/config/invokemanager.cnf ) and replace with this content:

<?xml version="1.0" encoding="UTF-8"?>
<IDataXMLCoder version="1.0">
  <record javaclass="com.wm.data.ISMemDataImpl">
    <array name="processorArray" type="value" depth="1">
      <value>org.wmaop.chainprocessor.AOPChainProcessor</value>
    </array>
  </record>
</IDataXMLCoder>

The key change here is the line <value>org.wmaop.chainprocessor.AOPChainProcessor</value>. This tells the Invoke Manager within Integration Server to call the wm-aop framework on every flow or Java service call.

If you are licensed and already testing with WmTestSuite you can run both together by adding the new AOP framework and the ServiceInterceptor reference.

<?xml version="1.0" encoding="UTF-8"?>
<IDataXMLCoder version="1.0">
  <record javaclass="com.wm.data.ISMemDataImpl">
    <array name="processorArray" type="value" depth="1">
      <value>com.wm.ps.serviceMock.ServiceInterceptor</value>
      <value>org.wmaop.chainprocessor.AOPChainProcessor</value>
    </array>
  </record>
</IDataXMLCoder>

After making the change restart the IS server.

Installation of the IS support package

  • OrgWmAOP Download

To test and verify the correct installation, install the OrgWmAOP package within IS, then invoke the verify service on the server with http://localhost:5555/rest/org.wmaop.verify changing the host and port appropriately. If installed correctly you should see:

status	Mocking framework operational

Installation video

Installation process. Please ensure you use the latest versions when performing the installations - versions in the video were correct at time of recording. ScreenShot

What can go wrong?

  • If you look in the invokemanager.cnf and the edited line has disappeared after starting IS this indicates that IS didn't find the class. Check the server.log for [ISS.0015.0002E] or "invokemanager.cnf" to see if it states class not found. If so, check paths for jars in correct location (E.g are the jars within the instance's lib/jars, not the server's lib/jars) and look for typos in the class name within the line added to invokemanager.cnf
  • Issues with unfound classes or strange interaction problems can be the result from a mismatch of framework library and package versions. Ensure you're using the latest of each jar and package if you're having problems.
  • If you're running 9.7 and see the error Error occurred while initializing server: java.lang.ClassCastException: org.wmaop.chainprocessor.AOPChainProcessor cannot be cast to java.lang.String this is likely due to running an unpatched version of IS. See PIE-33873 on Empower which indicates there's a fix available in IS_9.7_Core_Fix1 (Or later) to resolve the problem.

Getting Help

Here to help so drop an email with your questions and feedback to info@wmaop.org

Clone this wiki locally