Topic
  • 3 replies
  • Latest Post - ‏2012-10-18T13:24:27Z by SystemAdmin
OliverWeimer
OliverWeimer
2 Posts

Pinned topic multiple engine connect in TDWC

‏2012-03-07T15:12:23Z |
Hello,

I need help with the following problem / situation.

Situation:

2 servers, each with a TDWC.
There are also 14 Master (3 on Server A and 11 on Server B) on the 2 servers.
Automatic creation of the LTPA key is disabled.
LTPA-key from Server A was exported and imported to all eWAS-instances on Server A and B.
The engine connections to the instances on server A are all successful.

When we try to connect to an engine of Server B, we get the following error message.
AWSUI0766E Test connection to PERMANENT : failed.
AWSUI0833E The operation could not be completed. There has been a communication failure.
The internal message is: AWSJCO005E WebSphere Application Server has given the following error: CORBA NO_PERMISSION 0x0 No; nested exception is:
org.omg.CORBA.NO_PERMISSION:
>> SERVER (id=19a38c61, host=schapi) TRACE START:
>> org.omg.CORBA.NO_PERMISSION: java.rmi.AccessException: ; nested exception is:
com.ibm.websphere.csi.CSIAccessException: SECJ0053E: Authorization failed for /UNAUTHENTICATED while invoking (Bean)ejb/com/ibm/tws/conn/engine/ConnEngineHome getEngineInfo(com.ibm.tws.conn.util.Context):1 securityName: /UNAUTHENTICATED;accessID: UNAUTHENTICATED is not granted any of the required roles: TWSAdmin vmcid: 0x0 minor code: 0 completed: No
>> at com.ibm.ws.security.core.SecurityCollaborator.performAuthorization(SecurityCollaborator.java:484)
>> at com.ibm.ws.security.core.EJSSecurityCollaborator.preInvoke(EJSSecurityCollaborator.java:218)
>> at com.ibm.ejs.container.EJSContainer.preInvokeAfterActivate(EJSContainer.java:3634)
>> at com.ibm.ejs.container.EJSContainer.preInvoke(EJSContainer.java:2937)
>> at com.ibm.tws.conn.engine.EJSRemoteStatelessConnEngine_da67e2e1.getEngineInfo(Unknown Source)
>> at com.ibm.tws.conn.engine._EJSRemoteStatelessConnEngine_da67e2e1_Tie.getEngineInfo(_EJSRemoteStatelessConnEngine_da67e2e1_Tie.java:173)
>> at com.ibm.tws.conn.engine._EJSRemoteStatelessConnEngine_da67e2e1_Tie._invoke(_EJSRemoteStatelessConnEngine_da67e2e1_Tie.java:102)
>> at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:621)
>> at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:474)
>> at com.ibm.rmi.iiop.ORB.process(ORB.java:503)
>> at com.ibm.CORBA.iiop.ORB.process(ORB.java:1571)
>> at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2703)
>> at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2577)
>> at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:62)
>> at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:118)
>> at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)
>> SERVER (id=19a38c61, host=schapi) TRACE END.
vmcid: 0x0 minor code: 0 completed: No.
It doesn't matter whether I use my personal account or the functional user. Both of them have all rights in the TDWC.

additional info:
TWS Version on Server A = 8.5.0 with FP3
TWS Version on Server B = 8.5.0 with FP1
OS = Solaris 10
Users, passwords, ports are all checked

goal:
Access to all TWS-Master (engines) from the TDWC on Server A.
Updated on 2012-10-18T13:24:27Z at 2012-10-18T13:24:27Z by SystemAdmin
  • Donatella
    Donatella
    171 Posts

    Re: multiple engine connect in TDWC

    ‏2012-03-12T14:13:28Z  
    Hi, which is the TDWC version that are you using?

    Thanks
  • OliverWeimer
    OliverWeimer
    2 Posts

    Re: multiple engine connect in TDWC

    ‏2012-03-19T10:33:41Z  
    • Donatella
    • ‏2012-03-12T14:13:28Z
    Hi, which is the TDWC version that are you using?

    Thanks
    Hello,

    the Version is 6.1.0.37 Express.

    Regards,

    Oliver
  • SystemAdmin
    SystemAdmin
    194 Posts

    Re: multiple engine connect in TDWC

    ‏2012-10-18T13:24:27Z  
    Hello,

    the Version is 6.1.0.37 Express.

    Regards,

    Oliver
    Did you ever get an answer to this.
    I am experiencing the exact same errors
    on TWS 8.5.1 FP003 using eWAS 6.1.0.37 whilst trying to connect a TDWC engine
    to my MDM. I have successfully connected to my BMDM. All users/parms/security settings
    checked OK.