IBM WebSphere Liberty
To prepare AM to run in WebSphere, change the AM
.war file to ensure that the AM upgrade process
is able to find the AM configuration files.
You must make this change whenever you deploy a new
.war file as part of an AM upgrade.
If you are installing on Windows, use slashes (
Create a temporary directory and expand the
AM-7.2.0.warfile. For example:
$ cd /tmp $ mkdir /tmp/openam && cd /tmp/openam $ jar xvf ~/Downloads/AM-7.2.0.war
bootstrap.propertiesfile in the
WEB-INF/classesdirectory of the expanded
# configuration.dir=line in the
bootstrap.propertiesfile to specify a path with read and write permissions. For example:
# This property should also be used when the system user that # is running the web/application server process does not have # a home directory. i.e. System.getProperty("user.home") returns # null. configuration.dir=/my/readwrite/config/dir
$ jar cvf ../AM-7.2.0.war *
In addition to preparing the AM WAR file, follow these steps to configure WebSphere for AM after you deploy AM into WebSphere:
Load classes from AM bundled libraries before loading classes from libraries delivered with Liberty:
In the WebSphere Liberty administration console, go to Explore > Configure > server.xml.
openamweb application, click Add Child, and select Classloader from the list.
In the Delegation field, select parentLast.
Save your work.
If your environment uses SOAP, add the SOAP-related properties to the JVM.
AM-config-dir, create a file named
jvm.options, and add the following properties:
-Djavax.xml.soap.MessageFactory=com.sun.xml.internal.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl -Djavax.xml.soap.SOAPFactory=com.sun.xml.internal.messaging.saaj.soap.ver1_1.SOAPFactory1_1Impl -Djavax.xml.soap.SOAPConnectionFactory=com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnectionFactory -Djavax.xml.soap.MetaFactory=com.sun.xml.internal.messaging.saaj.soap.SAAJMetaFactoryImpl -Dcom.ibm.websphere.webservices.DisableIBMJAXWSEngine=true