isCOBOL for Axis2.war Directory hierarchy axis2.war is available in WAR (Web Archive) Distribution. The server side of isCOBOL for Axis2 ships as a J2EE application, and has the following structure: axis2-web META-INF WEB-INF classes conf axis2.xml lib activation.jar ... iscobol.jar ... xmlSchema.jar modules modules.list addressing.mar ... soapmonitor.mar services services.list aservice.aar ... version.aar web.xml Starting at the top, axis2-web is a collection of JSPs that make up the isCOBOL for Axis2 administration application, through which you can perform any needed actions such as adding services and engaging and disengaging modules. The WEB-INF directory represents the actual isCOBOL for Axis2 application, including all of the *.jar files, any included modules, and even the deployed services themselves. The classes directory holds any classes or properties files that are needed by isCOBOL for Axis2 itself, such as log4j.properties. Any actual services to be handled by the system reside in the services directory in the form of an axis archive, or *.aar file. This file contains any classes related to the service, as well as the services.xml file, which controls any additional requirements, such as the definition of message senders and message receivers. But the main file in all this it is axis2.xml, which controls how the application deals with received messages. It defines message receivers and transport receivers, as well as defining transport senders and determining which modules are active. It also defines the order of phases, and the handlers to be executed within each phase. You can control all of this information through the use of the Web application, but if you restart the isCOBOL for Axis2 application, these changes are lost and the server goes back to the definitions in the axis2.xml file.
