|
Problem(Abstract) |
If you are installing WebSphere® Application Server for
z/OS® V5.1 with security enabled you may see the following error messages
upon startup:
BBOO0220E SECJ0321E: Role based authorization is caller in role failed for
security name <null>, accessId NO_CRED_NO_ACCESS_ID, and role name
administrator.
BBOO0220E ADMR0021E: User <null> does not have the required role for
accessing restricted document cells/TST_Network/security.xml.
BBOO0222I ADMR0016I: Document cells/TST_Network/security.xml was modified
by user TST/WTDMCR.
BBOO0220E SECJ0321E: Role based authorization is caller in role failed for
security name <null>, accessId NO_CRED_NO_ACCESS_ID, and role name
administrator.
BBOO0220E ADMR0021E: User <null> does not have the required role for
accessing restricted document cells/TST_Network/security.xml.
Following are the messages from the Node Agent:
ADMS0016I: Configuration synchronization failed.
ADMS0016I: Configuration synchronization failed.
The Node Agent also reports filetransfer problems during the same time,
as shown below:
BBOO0222I ADFS0134I: File transfer is configured with
host="USCT.CUSTOMS.TREAS.GOV",
port="10013", securityEnabled="true".
com.ibm.ws.management.filetransfer.client.FileTransferClientImpl
SYSTEM=USCT SERVER=WTINAG
PID=0X0303006B TID=0X14F3EF00 0X000038 c=UNK
BBOO0222I ADFS0134I: File transfer is configure with
host="USCT.CUSTOMS.TREAS.GOV",
port="10013", securityEnabled="true".
com.ibm.ws.management.filetransfer.client.FileTransferClientImpl
SYSTEM=USCT SERVER=WTINAG
PID=0X0303006B TID=0X14F3EF00 0X000038 c=UNK
./bborjtr.cpp+830 ... BBOO0223I RemoteStream Exception
com.ibm.websphere.management.filetransfer.client.FileDownloadInputStream
com.ibm.
websphere.management.filetransfer.client.FileDownloadInputStream
SYSTEM=USCT SERVER=WTINAG
PID=0X0303006B TID=0X14F3EF00 0X000038 c=UNK
BBOO0220E ADFS0119E: An unexpected exception occurred:
java.io.IOException: An error occurred trying to create the FileTransfer
cookie.
Looking at the times, you can see that the synchronizations failed the
same time the errors occurred in the Deployment Manager. |
|
|
|
Cause |
Security was enabled for the Deployment Manager, but it
was not enabled for the Node Agent. |
|
|
Resolving the
problem |
You can resolve this problem by ensuring that Security is
enabled for the Deployment Manager and Node Agent. |
|
|
|
|
|
|