Cleaning the DataStage Server

Below are the list of the things you will have to do to safely clean and restart your server.


The first task (in UNIX and WINDOWS) that you will have to perform is to stop the Datastage services.  The services that have to be stopped are the dsrpc service,  dstelnet service, DSEngine service,  ASBAgent service and Logging Agent service.



Stopping DataStage Server

In Windows this is simple. If you have administrator privileges then all you have to do is to go to the services tab (type services.msc in the run command) and close each service one by one.

In UNIX its not that simple. First, you will have to log in as the root user. You will then need to navigate to the dshome directory. This location will be specified in the .dshome file which will be present in the / (root) directory. By default this will be /opt/IBM/InformationServer/Server/DSEngine. You will then have to run the dsenv file using the command shown below

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

Or

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

Once this has been set you can go ahead to run the commands required for a restart. You should first run the
command which will stop the Datastage services.
If you are in the home directory ( as specified in the .dshome file) then you should navigate to the bin directory and run the following command

.  /opt/IBM/InformationServer/Server/DSEngine/bin/uv –admin –stop

After that is done you will have to stop the ASB Agent and Logging agent. Do this by running the below command

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

Now all your services have been stopped in UNIX.

Windows has it easier since the services page is the one stop shop to stop all these services.
After the services have been stopped, you will have to stop you Websphere Application Server.


Stopping WebSphere Application Server

In Windows you can go to command prompt and run the stopserver.bat file using the following command

{Datastage Home Dir}/../../../WebSphere/AppServer/bin/stopServer.bat server1 sh -username <WAS_Username> -password <WAS_Password>

If you have the necessary access you might not even need to pass the username and password detail.

In UNIX, you should run the following command.

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

This will ensure that your Websphere application server has been stopped.


Cleaning

Once this is done you can start the activity of cleaning up your server. Identify processes related to nutcsrv4 (WINDOWS), dsapi_server, dsapi_slave,osh and uvsh.

ps –ef | egrep –i ‘nutcsrv4| dsapi_server| dsapi_slave|osh| uvsh’

Kill all if any process is there running on.

After this you can remove unwanted files as part of your cleanup

- Remove files from the folder {DatasageHome}/UVtemp
- Remove files from folder C:/Program Files/MKS Toolkit/fifos/  if your server is on windows
- Remove files from D:/tmp/  if server is on windows. Else remove the data from /tmp if your server is on UNIX
- Remove files from resource scratch disks and resource disks. These can be identified in your APT_CONFIG_FILE
- Remove files from each project PH folder ‘…/Srever/Projects/{Projetname}/&PH&

If your server is on Windows and you want to restart your server then kill the services MKS Rlogind, MKS Secure Shell Service and the NutCracker Service before you restart the Windows Server else your server might hang.



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