Enterprise Application Integration ( Eai )

Enterprise Application Integration ( EAI ) Server / Connector Restart – the most hardest job !!!

Our Production Servers • Connector / Adapter Server ( 59.163.6.71 / 5522 ) • ICS Server ( 59.163.6.70 / 5522 )

Login / password ? adapter server – eaiuser / eai321 ics server – eaiuser / vsnl@321 How to connect ?

Putty

Connectors • JDBC • JMS • Web-Services • LDAP • Broker

Connectors • JDBC • JMS DSLIMASAP P_RTBL1 • Web-Services P_RTBL2 P_RTBL3 • LDAP P_RTBL4 RTBL1 RTBL2 • Broker P_POS1 P_POS2 P_CRM1 OPNT1

Connectors • JDBC • JMS • Web-Services COP • LDAP CRM1 CRM2 • Broker FSBL MCC MIP

Connectors • JDBC • JMS • Web-Services • LDAP POS • Broker RMDY1 WSC1 WSC2 WSC3

Connectors • JDBC • JMS • Web-Services • LDAP • Broker LDAP

Connectors • JDBC • JMS • Web-Services • LDAP • Broker EMAIL DLP1 RTBL1

Connector logs Where Connector logs resides ? /icslogs// e.g. “WSC1” connector logs resides /icslogs/WebServices/WSC1 What is the name of connector trace file ? e.g. “WSC1” connector trace file WebServices_WSC1Connector.trc Note : In the name of trace file no “Arc” should be present

√ WebServices_WSC1Connector.trc × WebServices_WSC1Connector_Arc_01.trc

Connector Running !!! 1. Go to the directory where connector log resides command :

cd /icslogs/WebServices/WSC1

2. Find the connector trace file using “ls” command command :

ls -lrt

3. Open the Connector log using “tail” command e.g. tail –f WebServices_WSC1Connector.trc 4.

Only “appolling” in the line ( no “paused” ) should be display with increasing timestamp then connector is running properly. Otherwise, some problem in Connector.

Start connector ( Manually ) 1. Go to the “/opt/IBM/WebSphereAdapters/connectors/” command. cd /opt/IBM/WebSphereAdapters/connectors/

2. Go to the connector type directory e.g. cd WebServices

3. Go the Connector directory e.g. cd WSC1

4. Start the Connector Starter Script e.g. nohup ./start_WebServices.sh &

Kill Connector 1. Find out proper Process-ID of the Connector e.g. ps –ef | grep WSC1

2. Kill the Connector using ProcessID e.g. kill -9 152525

Note : Please do this Very Carefully. Carefully

Start Nanny of Connector 1.

Go to the Nanny directory command. cd /icslogs/nanny

2.

Go to the type of Connector directory e.g. cd WebServices

3.

Go to the Connector Directory e.g. cd WSC1

4.

Start Nanny Script of Connector e.g. nohup ./WebServices_WSC1nanny.sh &

Note : If Nanny starts connector will start automatically. Please checks logs of Connector to confirm of the status.

Some Points when we Start ICS Server

If the one or more connector don’t start properly after several tries. paused state comes again & again. connectors cannot binds itself properly to Server.

Stop ICS Server Go to the ICS Server Bin directory command : cd /opt/IBM/WebSphereICS/bin

Stop ICS Server using ics_manager command : ics_manager -stop

Find Persistent-Name Server Process ID e.g. ps –ef | grep 14510

Stop Persistent-Name Server by killing Process-ID e.g.

kill -9 548752

Start ICS Server Go to the ICS Server Bin directory command : cd /opt/IBM/WebSphereICS/bin

Start Persistent-Name Server Process-ID command : nohup ./PersistentNameServer.sh &

Start ICS Server using ics_manager command : ics_manager -start