Java Artifact Mapping in My webMethods Server
At run time, My webMethods Server creates a relationship between logged issues and the mapped components and products that are deployed on the server.
Whenever a server instance is created, a new layered product is installed, or during an upgrade of My webMethods Server, the Software AG Installer automatically invokes the following command, which generates a new My webMethods Server class path:
/MWS/bin/mws.bat -s server_instance_name update
When the server is updated, a javaArtifactMapping.xml file is also created and stored in the installation directory at:
Software AG_directory/MWS/server/server_instance_name/config
The
javaArtifactMapping.xml file contains the mapping between all of the available Java classes or packages and their corresponding Java artifacts such as jars, portlets, and web applications. The
loganalyzer command-line tool uses the updated
javaArtifactMapping.xml file when it analyzes and displays the information. For more information, see
loganalyzer.
Important: | If any custom components are deployed into the My webMethods Server instance after you executed the update command, the javaArtifactMapping.xml might not contain the information about the new custom components. For more information, see Updating the Java Artifact Mapping
File. |
The javaArtifactMapping.xml file stores the mapping information about the installed JAR files and layered products in the following elements:
<jar name="JAR_name" relative_path="install_path" build_number="value"
productId="product_install_ID">
<class name="class_name"/>
.
.
. </jar>
<product id="product_install_ID" displayName="product_display_name"
version="product_version"/>
Contact Support
|
Community
|
Feedback