If you are planning to enable WebSphere® Application Server global security after installing the Monitor Server, you must first update the authentication alias with a valid user ID and password.
When you install the Monitor Server in an unsecured WebSphere Application Server environment, the Launchpad creates an authentication alias in the WebSphere Application Server: MonitorBusAlias. This alias contains a default user ID called messaging.
If you enable the WebSphere Application Server global security after installation without updating the MonitorBusAlias alias with a valid User ID and password (with authority to access the WebSphere Application Server), a ResourceAllocationException exception will be thrown when you restart the WebSphere Application Server after enabling global security. The Monitor Server application will not start.
Refer to the topic named Security considerations for service integration buses in the WebSphere Application Server for details.
Refer to the topic named Java™ 2 Connector authentication data entry settings in the WebSphere Application Server documentation for details.
Refer to the topic named Security considerations for service integration buses in the WebSphere Application Server documentation for details.
Refer to the topic named Default messaging provider settings in the WebSphere Application Server documentation for details.
Refer to the topic named Adding a service integration bus link in the WebSphere Application Server documentation for details.
$AdminTask addUserToForeignBusRole { -bus ${PROCESS_SERVER_BUS_NAME} -foreignBus ${MONITOR_SERVER_BUS_NAME} -role Sender -user ${USER_NAME} }
$AdminTask addUserToDestinationRole { -type foreignDestination -bus ${PROCESS_SERVER_BUS_NAME} -foreignBus ${MONITOR_SERVER_BUS_NAME} -destination Monitor_Bus_Queue_Destination -role Sender -user ${USER_NAME} }
$AdminConfig save