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.
In Windows, running as services that are named ASBAgent.
ASB agents
include:
Connector access services
agent
Conveys service requests between the ODBC driver
components on the engine tier and the connector access services component on
the services tier.
InfoSphere Information
Analyzer agent
Conveys service requests between the engine
components on the engine tier and the InfoSphere Information
Analyzer services component on the services tier.
InfoSphere Information
Services Director agent
Conveys service requests between the engine
components on the engine tier and the InfoSphere Information
Services Director services component on the services tier.
ASB Agent only exists on the engine tier. There is no ASB Agent on the client tier.
It is the "gateway" between the domain server (ASB Server) and the engine tier.
Here
are some of the main ASB Agent use cases (but this is not an exhaustive list):
- At design time by DataStage when new connectors are used in a job design. For example, a "view data" of a new connector from the Designer will go through the domain server and the ASB Agent to "run" the connector on the engine tier in order to perform the view data.
- At runtime by Information Analyzer to run and control the DataStage jobs created for certain column analysis.
- At design time by Information Services Director to browse the ISD enabled DataStage jobs available on a given DataStage engine.
- At runtime by Information Services Director to pass the service request/response to and from the service provider (DataStage job or DB query).
- At design time by DataStage when new connectors are used in a job design. For example, a "view data" of a new connector from the Designer will go through the domain server and the ASB Agent to "run" the connector on the engine tier in order to perform the view data.
- At runtime by Information Analyzer to run and control the DataStage jobs created for certain column analysis.
- At design time by Information Services Director to browse the ISD enabled DataStage jobs available on a given DataStage engine.
- At runtime by Information Services Director to pass the service request/response to and from the service provider (DataStage job or DB query).
2) Logging agent
Logs events to the metadata repository.
In Linux, it is running as daemons that are named
LoggingAgent.
In Windows, running as services that are named LoggingAgent.
In Windows, running as services that are named LoggingAgent.
3) dsrpcd (DSRPC Service)
Allows InfoSphere DataStage
clients to connect to the server engine.
In Linux, It is running as a daemon (dsrpcd).
In
Windows, It is running as the DSRPC Service.
4) DataStage engine resource service
Establishes the shared memory structure that is
used by server engine processes.
5) DataStage Telnet service
Allows users to connect to the server engine by
using Telnet. Useful for debugging issues with the server engine. Does not need
to be started for normal InfoSphere DataStage processing.
In Windows, It is running as a DSTELNET Service.
njoy the simplicity.......
Atul Singh
No comments :
Post a Comment