JManage Installation

From jManage

Basic

1. You need to have JDK 1.5 to run jManage 2.0 (JDK 1.4 can be used for version 1.0). Note that you need JDK, not JRE.

2. Set JAVA_HOME to JDK 1.5 installation directory.

3. Unjar jmanage-XXX.jar to an installation directory.

4. If you are installing jmanage on unix environment, make all .sh scripts (under bin directory) executable:

    > chmod  x *.sh

5. Go to jManage "bin" directory and run "keygen". This prompts for a password which will be used to start the server. This password is also the "admin" user password. If you are using jManage for non-production environment, you can skip this step and use "123456" as the admin user password.

6. By default, jManage starts on port 9090. You can change this by modifying jetty-config.xml in config directory.

7. Run "startup" from the jManage "bin" directory and enter password configured in the previous step. This starts the jManage server. Use admin/123456 if you didn't run "keygen".

8. Access the server with URL "http://<server name>:9090".

9. Login to the application with username as "admin" and with configured password. Default password for admin is 123456.

10. Now configure your applciations to manage or monitor through jManage. Note that you will need to copy required app server specific jars in modules/<module> directory. This is a one time setup and is a must for websphere and weblogic (see below). You will need to restart jManage after copying required jars.

11. To shutdown, you can execute "shutdown" command from bin directory. You will be required to enter admin password.

Setup for JBoss

jManage ships with JBoss 3.2.x jars. If you are using JBoss 4.x, you will need to copy the following jars from 4.x installation:

1. jbossall-client.jar

2. jboss-jmx.jar

As of 2.0, JBoss 4.x jars are bundled with jManage.

Setup for Bea WebLogic

For connecting to weblogic, you need to copy weblogic.jar to modules/weblogic directory.

Setup for IBM Websphere

jManage uses SOAP connector for Webshere. For connecting to websphere, you need to copy the following jars to modules/websphere directory:

1. <websphere_install_dir>\WebSphere\AppServer\etc\tmx4jTransform.jar

2. <websphere_install_dir>\\WebSphere\AppServer\java\jre\lib\ibmcertpathprovider.jar

3. <websphere_install_dir>\\WebSphere\AppServer\java\jre\lib\ext\ibmjceprovider.jar

4. <websphere_install_dir>\\WebSphere\AppServer\lib\admin.jar

5. <websphere_install_dir>\\WebSphere\AppServer\lib\bootstrap.jar

6. <websphere_install_dir>\\WebSphere\AppServer\lib\classloader.jar

7. <websphere_install_dir>\\WebSphere\AppServer\lib\client.jar

8. <websphere_install_dir>\\WebSphere\AppServer\lib\emf.jar

9. <websphere_install_dir>\\WebSphere\AppServer\lib\ffdc.jar

10.<websphere_install_dir>\\WebSphere\AppServer\lib\j2ee.jar

11.<websphere_install_dir>\\WebSphere\AppServer\lib\mail-impl.jar

12.<websphere_install_dir>\\WebSphere\AppServer\lib\management.jar

13.<websphere_install_dir>\\WebSphere\AppServer\lib\ras.jar

14.<websphere_install_dir>\\WebSphere\AppServer\lib\sas.jar

15.<websphere_install_dir>\\WebSphere\AppServer\lib\security.jar

16.<websphere_install_dir>\\WebSphere\AppServer\lib\soap.jar

17.<websphere_install_dir>\\WebSphere\AppServer\lib\utils.jar

18.<websphere_install_dir>\\WebSphere\AppServer\lib\wasjmx.jar

19.<websphere_install_dir>\\WebSphere\AppServer\lib\wsexception.jar

20.<websphere_install_dir>\\WebSphere\AppServer\lib\wasproduct.jar

21.<websphere_install_dir>\\WebSphere\AppServer\lib\wsprofile.jar

22.<websphere_install_dir>\\WebSphere\AppServer\lib\wssec.jar

23.<websphere_install_dir>\\WebSphere\AppServer\lib\wssoap.jar

Setup for JSR160

There is no additional setup required for connecting to an application which supports JSR160.