Steps to help resolve administrative console problems In Websphere Application Server

Is the administrative console installed properly?

check the the following directory:

install_root/profiles/profile_name/logs/webui_config.log

Make sure you have the following statement at the bottom of the file:

Application adminconsole installed successfully

Are you having problems bringing up the administrative console?

make sure the administrative console is installed and started. Check the following directory:

install_root/profiles/dmgrProfile/SystemOut.log

Make sure you see the following statement:

Application started: adminconsole

Are you having problems bringing up the administrative console on port 9060, or do you want to make sure the administrative console is defined and running on port 9060?

By default the HTTP Transport port for the administrative console is set to 9060. If for some reason you have modified the port during install or after the install, then to find the administrative console port search for "WC_adminhost" in the serverindex.xml file under the following directory:

install_root/profiles/dmgrProfile/config/cells/cell_name/nodes/dmgrNode/

Remember, the administrative console port should also be listed in the virtualhosts.xml file under the following directory:

install_root/profiles/dmgrProfile/config/cells/cell_name

If you have modified the serverindex.xml file manually, or from the administrative console, make sure you modify the virtulahosts.xml file also and recycle the server

After the administrative console came up successfully, are some of the links missing or some of the pages are blank? 

it is not possible to reinstall the administrative console for WebSphere Application Server V6.0 unlike the V5.0 or V5.1 administrative console. To resolve the problem, stop the server and then remove the content from the following directory:

install_root/profiles/profile_name/wstemp

Replace the following file with the working adminconsole.ear file from another system:

install_root/systemApps/adminconsole.ear

Make sure both the versions and other products on WebSphere Application Server are identical. Start the server again.

“Effort only fully releases its reward after a person refuses to quit.”

Regards,

Akhilesh B. Humbe

How do I manually Stop/Start services on Unix/Linux in IBM InfoSphere Information Server (IIS) For DataStage?

Here are the instructions for restarting the Services, ASBAgent and DataStage engine in IIS v8 (see instructions below for each step). Please be advised that if any other packs are active (SAP R/3 Pack, SAP BW Pack, etc.) you will need to consult the documentation specific to those items for instructions.

The order in which to stop all services is:

Stop DataStage Engine

Stop the ASB Agent

Stop the WebSphere Application Server (WAS)

Here are the step-by-step instructions for each of the above.

Stop DataStage Engine

Log into your UNIX machine as root Make sure that no one is using DataStage. Check if there are any processes left

ps -ef | grep -i phantom

ps -ef | grep dsapi

ps -ef | grep dscs

These commands should not return any results. If they return results, it means that there are still some processes running. You can wait for the users to stop their processes or kill the processes (using kill -9 PID).

Check if dsrpc is running

netstat -a | grep dsrpc

If dsrpc is running, then you should get a line with the status LISTEN. If you get more lines it means that there are still some connections and you need to wait. If you see that dsrpc or other connections are in status WAIT then you also need to wait until this it disappears (you can also reboot the machine).

Stop DataStage Services using (use the dsengine credential for your system, default/typical is dsadm you have to run this from $DSHOME)

. ./dsenv

bin/uv -admin -stop

Then see if there is any memory segment left:

ipcs -mop | grep ade

For 64-bit Linux, use: ipcs -qms -a

If you get a result, take note of the PID and remove it (you will need root access)

ipcrm -m PID

Then, check the port again using

netstat -a | grep dsrpc

You should not get any result. If you get any results and the dsrpc is in WAIT state, then you need to wait until it disappears (you can also reboot the machine).

Stop the ASB Agent (you need to be root user)

Go to <path to>/IBM/InformationServer/ASBNode/bin Run

./NodeAgents.sh stop

Type 'yes' if you receive the following message:

rm: remove write-protected regular file `Agent.pid'?

Check the agent has stopped:

ps -ef | grep -i agent

On Solaris it may be necessary to run this command if errors similar to this are returned when trying to start the agent.

"com.ascential.acs.logging.agent.LoggingAgentSocketImpl.main(LoggingAgentSocketImpl.java:115) Caused by: java.net.BindException: Address already in use"

/usr/ucb/ps -auxww | grep java

3.     Stop the WebSphere Application Server (you need to be root user)

Go to <path to>/IBM/InformationServer/ASBServer/bin Run

./MetadataServer.sh stop Be sure the java processes go away Now check there are no java processes left behind:

> ps -ef | grep java

remove them if any exists with: > kill PID (NO -9)

The order in which to start all services is:

Start WebSphere Application Server (as root)

Start ASB Agent (as root)

Start DataStage Engine (use the dsengine credential for your system, default/typical is dsadm )

Here are the step-by-step instructions.

Start WebSphere Application Server (you need to be root user)

Note: for AIX platform, do the following:

unset LDR_CNTRL

create a file in ASBServer/bin named MetadataServer_env.sh and add the following line:

ulimit -n 10240 Go to <path to>/IBM/InformationServer/ASBServer/bin Run

./MetadataServer.sh run

Start ASB Agent (you need to be root user)

Go to <path to>/IBM/InformationServer/ASBNode/bin Run

./NodeAgents.sh start

Start DataStage Engine

 

(use the dsengine credential for your system, default/typical is dsadm)

Go to $DSHOME . ./dsenv Run

bin/uv -admin -start

Thanks & Regards,

Akhilesh Humbe