E1: SVM: WAS: WebSphere 18.104.22.168 Secure Profile, Server Manager Unable To Detect Status Of Servers Correctly
(Doc ID 1262748.1)
Last updated on JANUARY 16, 2020
Applies to:JD Edwards EnterpriseOne Tools - Version 8.98 and later
Microsoft Windows x64 (64-bit)
WebSphere Application Server 7.0 with applied Fix Pack 11 (or higher) and have created a Secure Profile. (Secure Profile is mandatory for EnterpriseOne BSSV Server.) Now you would like to manage the profile (Create J2EE Containers, Start, Stop, View Status of Servers) via Server Manager. You would also like to manage EnterpriseOne WebComponents (deploy, change component, un-deploy EOne web components) into servers within this profile using Server Manager.
Configured the soap.client.properties file with the WebSphere Administrator UserID/Password (file located under X:\IBM\WebSphere\AppServer\profiles\<profile_name>\properties directory on Windows and equivalent directories under UNIX):
soap.client.props file (check following properties):
Imported the Signer Certificates & Personal Certificates into the DummyClientTrustFile.jks and DummyClientKeyFile.jks (files located under C:\IBM\WebSphere\AppServer\profiles\AppSrv02\etc directory on Windows and equivalent directories under UNIX) using iKeyman utility.
Restarted the Admin Server of WebSphere (i.e server1) and the Server Manager Agent on the machine. The status of the Admin Server is not displayed correctly from Server Manager. The status of the Admin Server is always seen as stopped even if the server is running as verified from the serverStatus.bat (or .sh file) utility.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document