Use the XML configuration command line client
We access xmlaccess.sh using a command line tool. This command line client is a separate program that connects to the server using http or https. Connecting via http to a remote server makes it possible to configure the portal remotely. For networks inside the DMZ, use a secure https connection.
WP_PROFILE/PortalServer/bin/xmlaccess.sh
Use xmlaccess.sh a machine that does not have portal installed
We can use xmlaccess.sh remotely from a machine that does not have portal installed. In this case copy the required files to the remote machine and configure the portal from there. All we need is a Java run time. However, we have to adapt the path settings in the shell scripts accordingly. These are the required files:
- PORTAL_HOME/base/wp.xml.client/bin/wp.xml.client.jar
- PORTAL_HOME/base/wp.base/shared/app/wp.base.jar
- PORTAL_HOME/base/wp.base/shared/app/wp.engine.impl.jar
- PORTAL_HOME/base/wp.base/shared/app/wp.utilities.streams.jar
- APPSERVER_ROOT/lib/j2ee.jar
- APPSERVER_ROOT/lib/bootstrap.jar
- APPSERVER_ROOT/lib/com.ibm.ws.runtime.jar
- APPSERVER_ROOT/plugins/j2ee.jar
- APPSERVER_ROOT/plugins/com.ibm.wps.emf.jar
- APPSERVER_ROOT/plugins/org.eclipse.emf.ecore.jar
- APPSERVER_ROOT/plugins/org.eclipse.emf.common.jar
- PORTAL_HOME/bin/xmlaccess.sh or PORTAL_HOME/bin\xmlaccess.bat
When we update the portal by installing fix packs, these files might be updated. In such cases make sure that you always use the most recent versions of these files.
See also
- Command line syntax of xmlaccess.sh
- Transfer portal configuration data using xmlaccess.sh
- Create and modify resources
- Activate portlets, portlet applications, and web applications
- Scheduling the delayed cleanup of portal pages
- Register predeployed portlets
- Remove users and groups
- Prepare the deletion of orphaned resources
Parent Work with xmlaccess.shRelated reference:
XML Syntax for using a secure connection with SSL