If the J2EE Agent does not appear in the Administration Console after the installation has finished, try one or more of the following:
If the import started and failed to complete, alink appears at the bottom of the table on the J2EE Agents page. Click this link to repair the import.
If your J2EE server is not running, the Administration Console cannot import the J2EE Agent. Start J2EE server and wait 30 seconds before trying to configure the agent in the Administration Console.
If you installed the J2EE Agent on a WebSphere server, make sure you have restarted the WebSphere server. The J2EE Agent does not import into the Administration Console until WebSphere is restarted.
If you are running WebSphere with additional Java 2 security checks, the agent cannot import into the Administration Console. In the WebSphere console, turn off the additional Java 2 security checks or create a policy that grants full access to the nesp application.