This appendix contains the following topics:
Section A.2, "Starting and Stopping the WebSphere Portal Administration Server (server1)"
Section A.3, "Starting and Stopping the WebSphere Portal Server"
Beginning with Tools release 8.97, management of the application servers can be performed through the JD Edwards EnterpriseOne Server Manager application. This is the recommended method for starting, stopping and configuring application and portal servers. For additional information about Server Manager, refer to the Server Manager Guide for Tools Release 9.1, which is available on My Oracle Support.
The collaborative portal can also be managed through the WebSphere Administration Server and command line commands like previous releases. This remains the only option for JD Edwards EnterpriseOne Xe and ERP8 installations.
Refer to the following Knowledge Document E1: SVM: WebSphere 7.0.0.11 Secure Profile, Server Manager Unable to Detect Status of Servers Correctly (Doc ID 1262748.1) inorder for Server Manager to detect the status of WebSphere_Portal server correctly.
Caution:
The Portal is installed with its own profile which, by default, is wp_profile. When starting and stopping server1 for portal and the WebSphere_Portal server, it is necessary to be in the wp_profile/bin directory. Portal services cannot be managed using the WAS default profile from the profiles/default/bin directory.To locate the scripts to start and stop the WebSphere Portal Administration Server (server1), navigate to this directory:
Log in to the Green Screen as PORTALUSR, type STRQSH,
/QIBM/UserData/WebSphere/AppServer/V7/ND/profiles/<PROFILE_NAME>/bin
From the above specified /bin directory, you can start server1 by entering this command:
startServer server1 -user wpsadmin -password wpsadmin
Note:
The security user credentials will not be required if you have correctly configured the credentials in the soap.client.props file. This is also a pre-requisite for Server Manager.From the above specified /bin directory, you can stop server1 by entering this command:
stopServer server1 -user wpsadmin -password wpsadmin
Note:
The security user credentials will not be required if you have correctly configured the credentials in the soap.client.props file. This is also a pre-requisite for Server Manager.To locate the scripts to start and stop the WebSphere Portal Server, navigate to this directory:
Log in to the Green Screen as PORTALUSR, type STRQSH,
/QIBM/UserData/WebSphere/AppServer/V7/ND/profiles/<PROFILE_NAME>/bin
From the above specified /bin directory, you can start the WebSphere Portal Server by entering this command:
startServer WebSphere_Portal
Note:
The security user credentials will not be required if you have correctly configured the credentials in the soap.client.props file. This is also a pre-requisite for Server Manager.From the above specified /bin directory, you can stop the WebSphere Portal Server by entering this command:
stopServer WebSphere_Portal -user wasadmin -password wasadmin
Note:
The security user credentials are not required if you correctly configured the credentials in the soap.client.props file. This is also a pre-requisite for Server Manager.