9.7 Unable to Federate WebSphere Custom Profile If Agent Already Installed

When a WebSphere server instance that is created one machine is federated into the deployment manager of another machine that already has server instances with J2EE Agent installed, the newly federated server instance not start. This is because, the security configuration changes that are performed apply to all the instances of the deployment manager and all the application server instances that are part of it.

To work around this problem, copy the following files from the $WAS_HOME$/lib folder of the machine that has agents installed, to the $WAS_HOME$/lib folder of the new machine, then restart the server: