DataStage Two, InfoSphere Information Server process start and stop

DataStage Sequence Articles

DataStage One, install

1 Basics to know about the process

name	Description
ASB Agent Process	Communication agent, which is to assist the communication between layer and layer, the default port is 31531, it runs as a background process in the engine layer and the client layer
ASB Records Agent Process	Its role is to log event information into the database of the metadata storage tier
DataStage engine Process	It is the core process that manages DataStage job tasks, caches, job resources
WebSphere application Server (WAS)	Web Application Server program, established using Java EE, XML, and Web service, which is responsible for initializing the connector and Web-based console (console), InfoCenter (Information Center)

2 Starting the Infosphere Information Server process

Start was
Start the was service under root user:

$ /opt/IBM/InformationServer/ASBServer/bin/MetadataServer.sh start$ ps -ef|grep java

When was is started, check the process information and see the process information similar to the following:

root 22151422        1   0 12:48:12  pts/2  0:52 /opt/IBM/WebSphere/AppServer/java/bin/java -Declipse.security -Dwas.status.socket=61870 -Dosgi.install.area=/opt/IBM/WebSphere/AppServer -Dosgi.configuration.area=/opt/IBM/WebSphere/AppServer/profiles/InfoSphere/configuration -Dosgi.framework.extensions=com.ibm.cds,com.ibm.ws.eclipse.adaptors -Xshareclasses:name=webspherev70_%g,groupAccess,nonFatal -Xscmx50M .....

Start the ASB Agent program

$ /opt/IBM/InformationServer/ASBNode/bin/NodeAgents.sh  startStarting LoggingAgent...LoggingAgent started.Starting Agent...Agent started.

When the agent process starts, check the process information if no client communicates with the server at this time, the ASB Agent process and the ASB record agent process port status should be listen,

$ netstat-a|grep 31533tcp 0 0 *.31533 * * listen$ netstat-a|grep 31531tcp 0 0 *.31531 * listen$ ps-ef|grep-i agentroot 21364806 19202464 0 12: 49:27 PTS/2 0:02/opt/ibm/informationserver/asbnode/bin/runagent-xbootclasspath/a:conf-djava.ext.dirs=apps/jre/ Lib/ext:lib/java:eclipse/plugins:eclipse/plugins/com.ibm.isf.client_8.5.0.0-djava.class.path=conf- djava.security.auth.login.config=/opt/ibm/informationserver/asbnode/eclipse/plugins/com.ibm.isf.client_8.5.0.0 /auth.conf-dcom.ibm.corba.configurl=file:/opt/ibm/informationserver/asbnode/eclipse/plugins/com.ibm.isf.client _8.5.0.0/sas.client.props-dcom.ibm.ssl.configurl=file:/opt/ibm/informationserver/asbnode/eclipse/plugins/ Com.ibm.isf.client_8.5.0.0/ssl.client.props-dcom.ibm.corba.enableclientcallbacks=true- Dcom.ibm.corba.fragmentsize=128000-class Com/ascential/asb/agent/impl/agentimpl Run root 9699638 1 1 12:49:2 5 pTS/2 0:02/opt/ibm/informationserver/asbnode/apps/jre/bin/java-duser.language=en-duser.country=us- djava.security.auth.login.config=/opt/ibm/informationserver/asbnode/eclipse/plugins/com.ibm.isf.client_8.5.0.0 /auth.conf-dcom.ibm.corba.configurl=file:/opt/ibm/informationserver/asbnode/eclipse/plugins/com.ibm.isf.client _8.5.0.0/sas.client.props-dcom.ibm.ssl.configurl=file:/opt/ibm/informationserver/asbnode/eclipse/plugins/ Com.ibm.isf.client_8.5.0.0/ssl.client.props-dcom.ibm.corba.enableclientcallbacks=true- Dcom.ibm.corba.fragmentsize=128000-classpath/opt/ibm/informationserver/asbnode/conf:/opt/ibm/informationserver /asbnode/eclipse/plugins/com.ibm.isf.client_8.5.0.0:/opt/ibm/informationserver/asbnode/eclipse/plugins/ com.ibm.isf.client_8.5.0.0/acs_client.jar:/opt/ibm/informationserver/asbnode/eclipse/plugins/ com.ibm.isf.client_8.5.0.0/acs_common.jar:/opt/ibm/informationserver/asbnode/eclipse/plugins/ Com.ibm.isf.client_8.5.0.0/isf_util.jar:/opt/ibm/informationserver/asbnode/eclipse/plugins/com.ibm.isf.client_8.5.0.0/isf_j2ee.jar:/opt/ibm/informationserver/asbnode/eclipse/plugins/ Com.ibm.isf.client_8.5.0.0/asb_utils.jar:/opt/ibm/informationserver/asbnode/eclipse/plugins/com.ibm.isf.client _8.5.0.0/asb_util_client.jar:/opt/ibm/informationserver/asbnode/eclipse/plugins/com.ibm.isf.client_8.5.0.0/ Com.ibm.ws.ejb.thinclient_7.0.0.jar:/opt/ibm/informationserver/asbnode/eclipse/plugins/com.ibm.isf.client_ 8.5.0.0/com.ibm.ws.security.crypto.jar Com.ascential.acs.logging.agent.LoggingAgentSocketImpl

Note: When the ASB startup is complete, it takes about 1 minutes to register the event to was, so it is not recommended to do an operation like testing the database connection and loading the data immediately after the boot completes.

Start DataStage Engine

$ uv -admin -start

After the engine process is started, if there are no client connections, the port status should be: LISTEN, and the DSRPCD daemon and resource_tracker process start.

$ netstat -a|grep dsrpctcp4       0      0  *.dsrpc                *.*                    LISTEN$ ps -ef|grep dsrpc    root 19792368        1   0 13:07:03  pts/2  0:00 /software/IBM/InformationServer/Server/DSEngine/bin/dsrpcd$ ps -ef|grep resource_tracker   dsadm 10485832        1   0 13:07:19      -  0:00 /software/IBM/InformationServer/Server/PXEngine/bin/resource_tracker

3 Stop infosphere Information Server process

Stop DataStage Engine

$ ps -ef|grep dsapi $ ps -ef|grep dscs$ ps -ef|grep -i phantom$ netstat -a|grep dsrpc

Before stopping the check Dsapi, DSCS, phantom process should have no output, check the DSRPC port only a status of the listen process, if there is established, similar to the following situation is that there is currently a client connected to the server, You need to wait for the client to close the connection or kill the connection.

tcp4       0      0  testHost.dsrpc       192.168.1.9.sftsrv    ESTABLISHEDtcp4       0      0  *.dsrpc                *.*                    LISTEN

Stop engine after client closes connection

$ uv -admin -stop

Then check again Netstat-a|grep DSRPC should have no output. If the process is forced to stop while the client is not shutting down, the connection process that is not closed has a status of wait, which indicates that the engine is not completely stopped.

netstat -a|grep dsrpctcp4       0      0  estHost.dsrpc       192.168.1.9.sftsrv    FIN_WAIT_2

Stop the ASB Agent program

$ /opt/IBM/InformationServer/ASBNode/bin/NodeAgents.sh  stop

Check the ASB Agent

$ ps -ef|grep -i agent

The result of the output should be no process information that contains the Asbnode path, if you try to stop it again.
Stop the WAS process

$ /opt/IBM/InformationServer/ASBServer/bin/MetadataServer.sh stop

Check was process

$ ps -ef|grep java

The result of the output should be no process information that contains the Asbserver path, if you try to stop it again.

4 Footsteps

The footsteps of the start

echo set dataStage environment.../opt/IBM/InformationServer/Server/DSEngine/dsenvecho start WebSphere Application Server/opt/IBM/InformationServer/ASBServer/bin/MetadataServer.sh startecho check there are java process are runningps -ef|grep javaecho start ASB Agent /opt/IBM/InformationServer/ASBNode/bin/NodeAgents.sh startecho check the agent has runningps -ef|grep -i agentecho start DataStage Services uv -admin -startecho checking datastage backgroup process..ps -ef |grep dsapips -ef|grep dscsps -ef|grep -i phantomps -ef|grep dsrpcecho checking datastage dsrpc portnetstat -a|grep dsrpcecho see any momery segment leftipcs ­qms ­a|grep ade

Stop the Footsteps

echo set dataStage environment.../opt/IBM/InformationServer/Server/DSEngine/dsenvecho checking datastage backgroup process..ps -ef |grep dsapips -ef|grep dscsps -ef|grep -i phantomecho checking datastage dsrpc portnetstat -a|grep dsrpcecho stop DataStage Services uv -admin -stop echo see any momery segment leftipcs ­qms ­a|grep adeecho check the port again netstat -a|grep dsrpcecho stop ASB Agent /opt/IBM/InformationServer/ASBNode/bin/NodeAgents.sh stopecho check the agent has stoppedps -ef|grep -i agentecho stop WebSphere Application Server/opt/IBM/InformationServer/ASBServer/bin/MetadataServer.sh stopecho check there are no java process left behindps -ef|grep java

5 Summary

The ASB Agent communication process assists layer-to-layer communication, and the ASB Agent record process logs event information to the database in the metadata storage layer; The DataStage engine process is the core process that is responsible for creating, managing jobs, caches, and resources; WebSphere Application Server (WAS) is a Infosphere Information Server Web-based application that is responsible for initializing connectors and web-based console, InfoCenter, and other tools. They work together, a component process stops working, which can affect the work of other components, such as the ASB process stop will affect the service side and the client's communication, causing the client to disconnect, a variety of editing and saving work can not be normal, may lead to data loss, So careful understanding of basic knowledge and working principles will help you master DataStage faster and better.

--the End (2015-09-24)

DataStage Two, InfoSphere Information Server process start and stop