Cognos 10.2.1 Installation and Intergration

[leompafe]

I am installing Cognos 10.2.1 and having no success integrating it with IBM Maximo 7.6.
My oracle maximo database is on a unix server and my content database is different from the Maximo oracle database but on the same Unix server .
From the IBM Cognos Configuration tool , I can test all the namespaces I created and they all work fine . I also test the content manager and it  is successful . The problem is when I log on to maximo →Intergration→object Structures and try to publish a reporting object as cognos Package it fails with the error below . I have opened aPMR with IBM going on 2 months now with no solution . So my last hope is here


at 7/18/16 14:55:51:937 EDT] 0000013f SystemOut     O 18 Jul 2016 14:55:51:937 [ERROR] [MAXUI01] [CID-UIASYNC-1] Error while invoking the Cognos Player class "ActionLogPlayer"

com.ibm.tivoli.maximo.report.cognos.metadata.exception.CognosHandlerException: BMXAA7409E - The transformed object structures cannot be published to the Cognos server. To determine the cause, check the product log files.

   ; nested exception is:

   java.net.ConnectException: Connection refused: connect

   at com.ibm.tivoli.maximo.report.cognos.metadata.player.CognosManager.updateMetadata(CognosManager.java:425)

   at com.ibm.tivoli.maximo.report.cognos.metadata.player.CognosManager.createModel(CognosManager.java:312)

   at com.ibm.tivoli.maximo.report.cognos.metadata.player.ActionLogPlayer.playScript(ActionLogPlayer.java:239)

   at com.ibm.tivoli.maximo.report.cognos.metadata.player.ActionLogPlayer.playScript(ActionLogPlayer.java:132)

   at com.ibm.tivoli.maximo.report.cognos.metadata.adapter.CognosHandler.invoke(CognosHandler.java:193)

   at psdi.iface.mic.InvokeChannel.invokeEndpoint(InvokeChannel.java:357)

   at psdi.iface.mic.InvokeChannel.invoke(InvokeChannel.java:103)

   at psdi.webclient.beans.intobject.IntObjectAppBean.PUBLISH(IntObjectAppBean.java:286)

   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:94)

   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)

   at java.lang.reflect.Method.invoke(Method.java:619)

   at psdi.webclient.system.session.AsyncProcess.run(AsyncProcess.java:171)

   at java.lang.Thread.run(Thread.java:853)

Caused by: java.net.ConnectException: Connection refused: connect

   at com.cognos.org.apache.axis.AxisFault.makeFault(AxisFault.java:102)

   at com.cognos.org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:155)

   at com.cognos.org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)

   at com.cognos.org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:119)

   at com.cognos.org.apache.axis.SimpleChain.invoke(SimpleChain.java:84)

   at com.cognos.org.apache.axis.client.AxisClient.invoke(AxisClient.java:166)

   at com.cognos.org.apache.axis.client.Call.invokeEngine(Call.java:2785)

   at com.cognos.org.apache.axis.client.Call.invoke(Call.java:2768)

   at com.cognos.org.apache.axis.client.Call.invoke(Call.java:2444)

   at com.cognos.org.apache.axis.client.Call.invoke(Call.java:2367)

   at com.cognos.org.apache.axis.client.Call.invoke(Call.java:1813)

   at com.cognos.developer.schemas.bibus._3.MetadataServiceStub.updateMetadata(MetadataServiceStub.java:6576)

   at com.ibm.tivoli.maximo.report.cognos.metadata.player.CognosManager.updateMetadata(CognosManager.java:422)

   ... 13 more

Caused by: java.net.ConnectException: Connection refused: connect

   at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:369)

   at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:230)

   at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:212)

   at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:191)

   at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:403)

   at java.net.Socket.connect(Socket.java:642)

   at com.ibm.jsse2.qc.connect(qc.java:365)

   at com.ibm.jsse2.qc.<init>(qc.java:96)

   at com.ibm.jsse2.SSLSocketFactoryImpl.createSocket(SSLSocketFactoryImpl.java:7)

   at com.ibm.websphere.ssl.protocol.SSLSocketFactory.createSocket(SSLSocketFactory.java:595)

   at com.cognos.org.apache.axis.components.net.JSSESocketFactory.create(JSSESocketFactory.java:92)

   at com.cognos.org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:192)

   at com.cognos.org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:405)

   at com.cognos.org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:139)

   ... 24 more

)

[MFGF]

I am installing Cognos 10.2.1 and having no success integrating it with IBM Maximo 7.6.
My oracle maximo database is on a unix server and my content database is different from the Maximo oracle database but on the same Unix server .
From the IBM Cognos Configuration tool , I can test all the namespaces I created and they all work fine . I also test the content manager and it  is successful . The problem is when I log on to maximo →Intergration→object Structures and try to publish a reporting object as cognos Package it fails with the error below . I have opened aPMR with IBM going on 2 months now with no solution . So my last hope is here


at 7/18/16 14:55:51:937 EDT] 0000013f SystemOut     O 18 Jul 2016 14:55:51:937 [ERROR] [MAXUI01] [CID-UIASYNC-1] Error while invoking the Cognos Player class "ActionLogPlayer"

com.ibm.tivoli.maximo.report.cognos.metadata.exception.CognosHandlerException: BMXAA7409E - The transformed object structures cannot be published to the Cognos server. To determine the cause, check the product log files.

   ; nested exception is:

   java.net.ConnectException: Connection refused: connect

   at com.ibm.tivoli.maximo.report.cognos.metadata.player.CognosManager.updateMetadata(CognosManager.java:425)

   at com.ibm.tivoli.maximo.report.cognos.metadata.player.CognosManager.createModel(CognosManager.java:312)

   at com.ibm.tivoli.maximo.report.cognos.metadata.player.ActionLogPlayer.playScript(ActionLogPlayer.java:239)

   at com.ibm.tivoli.maximo.report.cognos.metadata.player.ActionLogPlayer.playScript(ActionLogPlayer.java:132)

   at com.ibm.tivoli.maximo.report.cognos.metadata.adapter.CognosHandler.invoke(CognosHandler.java:193)

   at psdi.iface.mic.InvokeChannel.invokeEndpoint(InvokeChannel.java:357)

   at psdi.iface.mic.InvokeChannel.invoke(InvokeChannel.java:103)

   at psdi.webclient.beans.intobject.IntObjectAppBean.PUBLISH(IntObjectAppBean.java:286)

   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:94)

   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)

   at java.lang.reflect.Method.invoke(Method.java:619)

   at psdi.webclient.system.session.AsyncProcess.run(AsyncProcess.java:171)

   at java.lang.Thread.run(Thread.java:853)

Caused by: java.net.ConnectException: Connection refused: connect

   at com.cognos.org.apache.axis.AxisFault.makeFault(AxisFault.java:102)

   at com.cognos.org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:155)

   at com.cognos.org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)

   at com.cognos.org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:119)

   at com.cognos.org.apache.axis.SimpleChain.invoke(SimpleChain.java:84)

   at com.cognos.org.apache.axis.client.AxisClient.invoke(AxisClient.java:166)

   at com.cognos.org.apache.axis.client.Call.invokeEngine(Call.java:2785)

   at com.cognos.org.apache.axis.client.Call.invoke(Call.java:2768)

   at com.cognos.org.apache.axis.client.Call.invoke(Call.java:2444)

   at com.cognos.org.apache.axis.client.Call.invoke(Call.java:2367)

   at com.cognos.org.apache.axis.client.Call.invoke(Call.java:1813)

   at com.cognos.developer.schemas.bibus._3.MetadataServiceStub.updateMetadata(MetadataServiceStub.java:6576)

   at com.ibm.tivoli.maximo.report.cognos.metadata.player.CognosManager.updateMetadata(CognosManager.java:422)

   ... 13 more

Caused by: java.net.ConnectException: Connection refused: connect

   at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:369)

   at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:230)

   at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:212)

   at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:191)

   at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:403)

   at java.net.Socket.connect(Socket.java:642)

   at com.ibm.jsse2.qc.connect(qc.java:365)

   at com.ibm.jsse2.qc.<init>(qc.java:96)

   at com.ibm.jsse2.SSLSocketFactoryImpl.createSocket(SSLSocketFactoryImpl.java:7)

   at com.ibm.websphere.ssl.protocol.SSLSocketFactory.createSocket(SSLSocketFactory.java:595)

   at com.cognos.org.apache.axis.components.net.JSSESocketFactory.create(JSSESocketFactory.java:92)

   at com.cognos.org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:192)

   at com.cognos.org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:405)

   at com.cognos.org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:139)

   ... 24 more

)

Hi,

The option to publish from Maximo to Cognos doesn't look like any standard Cognos technology to me. The clue is in the first few lines of the error, which refer to "com.ibm.tivoli.maximo.report.cognos.metadata.player.CognosManager.updateMetadata"

It looks to me like there's a Maximo utility that does the publishing, and this might not be configured correctly. Sadly I know nothing about Maximo to be able to suggest how to help here. A quick google search turned up the following, which might be a starting point:

http://www-01.ibm.com/support/docview.wss?uid=swg21577745

Cheers!

MF.

[leompafe]

Thanks , I tried that and it did not help .
Hoping to get someone here who has had a similar issue

[MFGF]

Thanks , I tried that and it did not help .
Hoping to get someone here who has had a similar issue

I'd suggest you log a PMR for this with IBM. Both Maximo and Cognos are IBM products, so there can be no "oh, it's not us it's the other guy" arguments

Good luck!

MF.

[Rosanero4Ever]

Hi leompafe,

Did you solve the issue?
I'm struggling with the same exception...