Skip to content

Building from source

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

Projects

There are a number of projects in the wmaop space that make up the testing solution. Generally, if the project begins with OrgWmAOP... then its a package for deployment on IS. The other all lower case projects are Java source for server or test functionality.

The projects consist of:

  • wm-aop - This is the core API framework that hooks into the IS service execution process and provides the functionality for mocking. The jar file built by this project is registered within Integration Server
  • wm-aop-util - Common utilities that provide functionality such as exposing the pipeline for conditional expressions
  • wm-parent - The parent project that has version information and build control, needed by all wm-* java projects
  • wm-jbehave - Interfacing code for the JBehave runtime execution of tests and interaction with the services in the OrgWmAOP IS package
  • OrgWmAOP - IS Package that exposes the wm-aop API as a set of Flow/RESTful services
  • OrgWmAOPTest - IS Package used when testing wm-jbehave and running the test stories to execute full functionality (Unit testing the unit testing framework!)
  • OrgWmAOPSample - An IS Package with samples to get started in understanding options when writing your own tests

Dependencies

In the current version, there are wM jar dependencies during the build that you need to register locally, either by loading the jars into your local Maven repository or having a file reference directly to the jars. The jars are only shipped with the product and therefore cannot be made available through normal download means. Register the following:

  • wm-isclient using SoftwareAG\common\lib\wm-isclient.jar
  • wm-isserver using SoftwareAG\IntegrationServer\lib\wm-isserver.jar
  • deployer-api using SoftwareAG\WS-Stack\lib\deployer-api-9.10.0.0.jar (Or the appropriate version for your release)
  • wm-g11nutils using SoftwareAG\common\lib\wm-g11nutils.jar
  • client-api using SoftwareAG\WS-Stack\lib\client-api-9.10.0.0.jar
  • wsstack-commons using SoftwareAG910\WS-Stack\lib\wsstack-commons-9.10.0.0.jar

The dependency structure and versions are shown in the pom.xml file.

Execution

For building each of the projects, see their relevant wiki pages for specific details

Simplifying local build

When building, use the localServer profile and supply is.server.lib.dir property as your IS server instance lib/jars to have the built jars update post build. Eg for is.server.lib.dir as D:\SoftwareAG\IntegrationServer\instances\default\lib\jars the dependant jars will be copied there and a quick restart of IS will reload.

Clone this wiki locally