stop ManagerServer1 with command prompt using SSL Port

Sagar Tippe

Hi All,

We have enabled SSL+SSO on analytics and EM/Console both. I know restart of OPMN is nothing to do with the SSL, but while stopping ManagedServer1 we need to put port number in command.

I'm able to stop ManagedServer1 using Non-SSL port with below command,

./stopManagedWebLogic.sh bi_server1 http://ip_address:7001

while doing the same using SSL port, it fails.

./stopManagedWebLogic.sh bi_server1 t3://ip_address:7002

An error message is below,

---------------------------------------------------------------------------------------------------------------------------------

Please enter your username :biadmin

Please enter your password :

Connecting to t3://ip_address:7001 with userid biadmin ...

Successfully connected to Admin Server 'AdminServer' that belongs to domain 'bifoundation_domain'.

Warning: An insecure protocol was used to connect to the

server. To ensure on-the-wire security, the SSL port or

Admin port should be used instead.

Shutting down the server bi_server1�t3s://ip_address:7002 with force=false while connected to AdminServer ...

No stack trace available.

This Exception occurred at Thu Feb 02 09:16:36 EST 2017.

weblogic.management.scripting.ScriptException: Error occured while performing shutdown : The server bi_server1�t3s://ip_address:7002 is not running.

Problem invoking WLST - Traceback (innermost last):

  File "/cs/obiee/bmr/app/middlewarehome/user_projects/domains/bifoundation_domain/shutdown.py", line 7, in ?

  File "<iostream>", line 1218, in shutdown

  File "<iostream>", line 1852, in raiseWLSTException

WLSTException: Error occured while performing shutdown : Error shutting down the server : Error occured while performing shutdown : The server bi_server1�t3s://ip_address:7002 is not running.

Use dumpStack() to view the full stacktrace

Done

Stopping Derby Server...

---------------------------------------------------------------------------------------------------------------------------------

I've already tried the Doc ID 2006141.1 to follow the same, but no luck :-(