How to find Agents Ports in IBM InfoSphere Server - Version.xml

The list of installed products can be obtained from the Version.xml file that is located in ISHOME directory on the client, engine and domain machines where InfoSphere Information Server is installed.

Default locations

UNIX /opt/IBM/InformationServer,
WINDOWS C:\IBM\InformationServer

Below is a example listing of the Version.xml file:

Error 39202 when logging into IBM DataStage

DataStage Client programs (Designer, Manager, Director) experience a connection failure, and the message displayed to the user is:

Failed to connect to host: xxxxx, project: UV
(Internal Error (39202))

More Warnings causes Low Performance in DataStage. WHY ???

 
Warning messages are bad in any programming language; more so, in the case of DataStage. 

This is because DataStage is typically used for large scale processing of data. Every time a warning message is encountered, the engine code has to encounter an exception handler, throw the warning message and resume its task. 

Changing Logs method in DataStage

DataStage logging was changed at release 8.1 to log job run detail records into the operational repository, (xmeta) rather than the local project level log files, (RT_LOGxxx).
In case XMETA repository logging causing problem (i.e not visible from designer), we able to change the logging method back to local project log files.

Websphere Application Server[WAS] log files

IBM Websphere Application Server creates the following log files trace.log ,SystemOut.log , and SystemErr.log , activity.log, StartServer.log , stopServer.log , native_stdout.log , native_stderr.log.

Let us see the above log files in details .

Restoring IBM Information Server components [DataStage]

If you backed up the files, directories, and databases associated with IBM Information Server, you can restore these components to recover your data in the event of hardware failure or other disaster.

This task assumes that you are starting on a clean computer on which IBM Information Server has not been installed. It also assumes that the host name of the computer is identical to that of the computer on which the backup was performed and that all components are being restored in the exact same location that they originally were in.

Backing up IBM Information Server components [DataStage]

You can back up the components of IBM Information Server to ensure that you can recover your data in the event of hardware failure or other disaster.

During installation, you are prompted to create an installer response file. It is useful to generate this file and store it in a backup location. If you need to reinstall IBM Information Server, you must use the same configuration as the original installation. If you have a copy of the installer file, you can pass the response file to the installer from the command line.

Error 81015 when logging into DataStage

Unable to connect to host error 81015 when logging into IBM InfoSphere DataStage (DS):

Failed to connect to host: <hostname>, project: UV
(The connection has timed out (81015))

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.

Service Agents in DataStage

1) ASB Agent

ASB agent is a Java background process run on the server or on the computer where the DataStage engine and client tiers are installed. When a service that runs on the Service tier receives a service request that needs processing on Information Server components then this agent receives this request and pass it on.

In Linux, it is running as daemons that are named ASBAgent.
In Windows, running as services that are named ASBAgent.