Manage Portal Scripting Interface in the cluster
The Portal Scripting Interface allows us to create administrative tasks that administrators can run from a command line. You must prepare your cluster to manage Portal Scripting Interface.To manage Portal Scripting Interface:
- Perform the following steps before using the Portal Scripting Interface for the first time:
- Verify the wp.wire.jar file is present in the WAS_HOME/lib directory on the dmgr machine.
- If the file is not present, copy the file from the WAS_HOME/lib directory on any node to the WAS_HOME/lib directory on the dmgr machine.
- Restart the dmgr.
- For z/OS : Before we use the Portal Scripting Interface for the first time:
- Mount the SMP/E home directory of WebSphere Portal, read only, on the dmgr node.
- Edit job EJPSSEWL with the SMP/E home directory of WebSphere Portal for #EJPSMPH# and with the WAS home directory of the dmgr node for #ASWASH#.
- Submit the job on the dmgr node.
- Upon completion, examine the job output. Success is indicated with "rc=0" in the job output.
- Restart the dmgr.
- Run the following task to connect the scripting client to the WAS Network Deployment SOAP port:
...where...
- ND SOAP Port is the WAS Network Deployment machine's SOAP connector-address.
To find the SOAP port, on the WAS admin console, navigate to System administration > dmgr > Ports > SOAP_CONNECTOR_ADDRESS.
For example, if we are running wpscript on a machine that is part of a cell managed by a dmgr, the SOAP port might be 8881.
- user is the WAS administrative user name.
- password is the administrative user password.
scripting client to the WAS Network Deployment SOAP
Operating system Task Windows wpscript.bat -port ND SOAP Port -user user -password password UNIX ./wpscript.sh -port ND SOAP Port -user user -password password IBM i wpscript.sh -port ND SOAP Port -user user -password password z/OS ./wpscript.sh -port ND SOAP Port -user user -password password Be logged in using the WebSphere admin user ID.
Parent: Manage the cluster