IT Process Automation

  • 1.  Agent not able communicate to Orchestrator ITPAM

    Posted May 29, 2015 11:03 AM

    Agent installed without issue , but when I opened the logs , below mentioned error was there .

     

    2015-05-29 20:19:53,864 ERROR [com.optinuity.c2o.util.SimpleCastorXMLUtil] [A Agent Startup] Mapping File serviceOperationMappingFilenot Found. This may be available at GUI or Source.

    2015-05-29 20:19:53,865 ERROR [com.optinuity.c2o.util.SimpleCastorXMLUtil] [A Agent Startup] SimpleCastorXMLUtil.getMapping: failed to find mapping serviceOperationMappingFile file: serviceOperationMappingFile

    2015-05-29 20:19:57,160 WARN  [com.optinuity.c2o.util.SSLCertificateUtilities] [A Agent Startup] Setup to accept all SSL Certificates

     

     

    Please help to fix this issue .



  • 2.  Re: Agent not able communicate to Orchestrator ITPAM

    Posted Jun 03, 2015 03:37 PM

    Can anyone help Kalpana with the issue?

     

    Thanks

     

    Agent not able communicate to Orchestrator ITPAM

     

    Agent installed without issue , but when I opened the logs , below mentioned error was there .

     

    2015-05-29 20:19:53,864 ERROR [com.optinuity.c2o.util.SimpleCastorXMLUtil] [A Agent Startup] Mapping File serviceOperationMappingFilenot Found. This may be available at GUI or Source.

    2015-05-29 20:19:53,865 ERROR [com.optinuity.c2o.util.SimpleCastorXMLUtil] [A Agent Startup] SimpleCastorXMLUtil.getMapping: failed to find mapping serviceOperationMappingFile file: serviceOperationMappingFile

    2015-05-29 20:19:57,160 WARN  [com.optinuity.c2o.util.SSLCertificateUtilities] [A Agent Startup] Setup to accept all SSL Certificates

     

     

    Please help to fix this issue .



  • 3.  Re: Agent not able communicate to Orchestrator ITPAM

    Broadcom Employee
    Posted Jun 03, 2015 04:35 PM

    Kalpana,

     

    Did you deselect "Use Deprecated comms" during or after the installation of the Agent so as to use simplified comms?

    If so, and you do not have PAM 4.2 SP02 CP01, then you need to uninstall the agent and delete the install folder on the Agent machine, then install the agent again and only use deprecated comms.

    If you require simplified comms, you need to upgrade to 4.2 SP02 CP01.

     

    ~Jennifer



  • 4.  Re: Agent not able communicate to Orchestrator ITPAM

    Posted Jun 04, 2015 02:26 AM

    Hi Jennifer,

     

    I did not deselect the  Use Deprecated comms  option  still I am getting this error and later on  when I checked the logs again below mentioned errors were there.

     

    Please help to fix

     

    2015-06-03 14:42:02,375 WARN    IO Error or connection aborted while executing request or processing HTTP response.

    org.apache.http.conn.ConnectTimeoutException: Connect to HCLT-PC2152-2.HCLT.CORP.HCL.IN:80 timed out

                    at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:129)

                    at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:180)

                    at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:151)

                    at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:125)

                    at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:645)

                    at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:480)

                    at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:906)

                    at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:805)

                    at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:784)

                    at com.optinuity.c2o.transport.Client.sendGet(Client.java:629)

                    at com.optinuity.c2o.transport.Resolver.isDomainContxtURLReachable(Resolver.java:1095)

                    at com.optinuity.c2o.transport.Resolver.getDomainTransportURL(Resolver.java:264)

                    at com.optinuity.c2o.transport.Resolver.getDomainTransportURL(Resolver.java:213)

                    at com.optinuity.c2o.c2oagent.AgentManager.getHeartbeatUrl(AgentManager.java:1273)

                    at com.optinuity.c2o.c2oagent.AgentManager.sendHeartbeatToDO(AgentManager.java:1304)

                    at com.optinuity.c2o.c2oagent.AgentManager.performConfigTimerOperation(AgentManager.java:1255)

                    at com.optinuity.c2o.c2oagent.AgentManager.access$000(AgentManager.java:124)

                    at com.optinuity.c2o.c2oagent.AgentManager$1.run(AgentManager.java:776)

                    at java.util.TimerThread.mainLoop(Unknown Source)

                    at java.util.TimerThread.run(Unknown Source)

     

     

     

    Thanks and Regards

    Kalpana



  • 5.  Re: Agent not able communicate to Orchestrator ITPAM

    Broadcom Employee
    Posted Jun 04, 2015 10:29 AM

    Kalpana:

    It is pretty evident from the error "Connect to HCLT-PC2152-2.HCLT.CORP.HCL.IN:80 timed out" that your agent is not able to reach your domain orchestrator. Is there a firewall blocking it?

    --

    Lokesh