Starting IBM Information Server [DataStage] and WebSphere Application services [WAS]

To start IBM Information Server and WebSphere Application services:

   1. Start WebSphere Application Server.

Windows

Click All Programs > IBM WebSphere > Application Server [v6/v7/..] > Profiles
> default > Start the server.

If you installed IBM Information Server in a different WebSphere Application Server profile, you must select the correct profile. Your path will vary if you installed IBM Information Server in a different location or used a different profile.

C:\IBM\WebSphere\AppServer\bin\profiles\default\bin\startServer.bat server1 
-username <WAS_Username> -password <WAS_Password>

Linux or UNIX

The path shown in this command assumes that the product is installed in the default location and uses the default WebSphere Application Server profile. Your path will vary if you installed IBM Information Server in a different location or used a different profile.

/opt/IBM/WebSphere/AppServer/profiles/default/bin/startServer.sh -username 
<WAS_Username> -password <WAS_Password> 

Note: When restarting WebSphere Application Server, regardless of the method used, the startup method will return prior to the server being fully started. Monitor the SystemOut.log file until the following entry is shown:

[5/1/08 15:10:20:591 EDT] 0000000a WsServerImpl A WSVR0001I: Server server1 open for e-business

You can find the SystemOut.log file in the locations listed below. The paths shown assume that the product is installed in the default location and uses the default WebSphere Application Server profile. Your path will vary if you installed IBM Information Server in a different location or used a different profile.

Windows

C:\Program Files\IBM\WebSphere\AppServer\profiles\default\logs\server1\SystemOut.log

Linux or UNIX

/opt/IBM/WebSphere/AppServer/profiles/default/logs/server1/SystemOut.log

Typically, the server will be fully started in 2 to 4 minutes after the startup method indicates that startup has completed.

1.            Start the following services: ASB Agent, Logging Agent, DataStage Telnet Service, DSRPC Server, and DataStage Engine Resource Service.

     The engine services will only be present if you installed both the services tier and the engine tier on the same machine.

Windows

Start these services in the order that they appear in the table.

Note: On Windows, you can use the Services Administrative Tool or the sc command line tool to start the services.

Order that services must be started
Service Full Name	Service Short Name
Logging Agent	LoggingAgent
ASB Agent	ASBAgent
DataStage Engine Resource Service	DSEngine
DataStage Telnet Service	dstelnet
DSRPC Service	dsrpc

Linux or UNIX

To start the services:

a.Run the following command to source the dsenv file. The paths shown in this command assume that the product is installed in the default location. Your path will vary if you installed IBM Information Server in a different location.

. /opt/IBM/InformationServer/Server/DSEngine/dsenv

The /.dshome file contains the current engine location. Because UNIX® systems support multiple instances of WebSphere DataStage®, ensure that /.dshome contains the engine that you want to restore. Otherwise, the bin/uv -admin -start command starts the instance of WebSphere DataStage that is in the /.dshome file.

b. Run the following commands to start the WebSphere DataStage services. The paths shown in these commands assumes that the product is installed in the default location and uses the default WebSphere Application Server profile. Your path will vary if you installed IBM Information Server in a different location or used a different profile.

c.
cd ./opt/IBM/InformationServer/Server/DSEngine

bin/uv –admin –start

d. Run the following commands to start the ASB Agent and the Logging Agent. The paths shown in these commands assume that the product is installed in the default location and uses the default WebSphere Application Server profile. Your path will vary if you installed IBM Information Server in a different location or used a different profile.

e. 
 cd /opt/IBM/InformationServer/ASBNode/bin

./NodeAgents.sh start

njoy the simplicity.......
Atul Singh