Page History

...

Windows    infra\bin\psin_cli.bat
                    -i3-user <user<user_name>name>
                    {-i3-encrypted-password <encrypted<encrypted_password> password> | -i3-clear-password <clear<clear_password>password>}
                    -action ssl-deployment
                    {-server <SSL <SSL target server>server>}
UNIX            ./infra/bin/psin_cli.sh
                    -i3-user <user<user_name>name>
                    {-i3-encrypted-password <encrypted<encrypted_password> password> | -i3-clear-password <clear<clear_password>password>}
                    -action ssl-deployment
                    {-server <SSL <SSL target server>server>}

Table 4-1 Elements of the deployment command

...

To monitor a remote J2EE instance, perform the following steps to install the J2EE remote instance:1.    Copy

1. Copy the deployment.zip file to the J2EE instance server.

...

1. Extract it to a local folder.

   Info

...

1. Verify that the JVM user has full permissions in the local folder, as the JVM must have access to the folder and files within it to initiate the installation of the J2EE instance. The files also contain the access key to the Precise installation and should only be accessible to the relevant JVM user.

   Info

...

1. You should keep one folder per monitored instance on the server.

...

1. Add the following JVM parameters to the JVM startup script, where

...

1. <LOCAL_

...

1. LIB> is the extracted directory name.

   ...

   1. 1. For WebSphere, see Installation on WebSphere.

   ...

   1. 1. For anything else:
         -javaagent:

   ...

   1. 1. <LOCAL-

   ...

   1. 1. LIB>/products/j2ee/lib/indepthj2ee-agent.jar
         Alternatively, you can run the displayParams script, which will generate the JVMparameter.

   ...

   1. 1. Info
         For more information on JVM arguments, see JVM arguments.

   ...

   1. Restart the JVM to initiate the instance installation.

   Anchor
   JVMarguments JVMarguments

   JVM arguments

   This section describes recommended guidelines to follow for the JVM aguments.
   •    All JVM arguments should appear as a single line.
   •    The format of the parameter generated by the displayParam script is
   -javaagent:<LOCAL-LIB>/products/j2ee/lib/indepthj2ee-agent.jar=com.precise.javaperf
   .javaagent.agents.DefaultJavaAgent
   NOTE    Use the correct file separator style for UNIX and Windows '\' or '/'.
   •    To use an instance name other than the server name, add -Djvm.name=<JVM-NAME>. For more information on what happens if the JVM name argument is not supplied, see JVM naming.
   •    You can optionally add -DPRECISE_SSL_APPLICATION=<APPLCIATION_NAME> to configure the instance application, and -DPRECISE_SSL_TIER=<TIER_NAME> to configure the instance Tier.
   •    To communicate with the SSL server using a proxy, you can add the following proxy parameters:
   -DPRECISE_SSL_PROXY_HOST=<PROXY_HOST>
   -DPRECISE_SSL_PROXY_PORT=<PROXY_PORT>
   -DPRECISE_SSL_PROXY_PROTOCOL=<PROXY_PROTOCOL>
   Supported values are  SOCKS, HTTP, and  DIRECT. The default value is SOCKS.
   JVM naming
   It is highly recommended to specify the JVM name in the JVM arguments as described in JVM arguments! If you did not follow the recommendation, the JVM name will be resolved automatically in the following way:
   •    For WebLogic and WebSphere JVMs running as WebLogic/WebSphere console managed servers correspondingly, the JVM name will be set to the server name if it was not specified explicitly.
   •    For the rest of the JVMs the JVM name will be set to <server_name>_<running_number>, where <server_name> is the name of the server on which the JVM runs, while <running_number> will help to distinguish between different JVMs running on the same server, but using different extracted Precise folders.
   •    ***(Requires testing and decision if we support this case!!!!)***If more than one JVM will be run on the same server using the same extracted Precise folder and for none of them the JVM name argument is supplied, the activity of both JVMs will be presented in the same invocations tree and the metrics values will be displayed as average values between all the JVMs.
   
   Shared script JVMs
   If several JVMs are sharing the startup script where Precise JVM arguments were added, all of them will be started up with the same JVM name, whether it was specified or not. In such case all the data of the JVMs will be presented in the same way as described in the third bullet of JVM naming.
   Advanced installation notes
   This section contains advanced installation notes.
   •    If you have uninstalled a remote J2EE instance, and you want to install it again, on the Precise FocalPoint remove the products/infra/var/<INSTANCE_NAME>_id.txt file from the local extraction folder, and restart the JVM.
   •    By default, the reinstalled instance includes history data from the previously uninstalled instance. If the server name or instance name has changed and you want the newly installed instance to include the history data of the previously uninstalled instance, you can add the following property after the removal of the products/infra/var/<INSTANCE_NAME>_id.txt file and before restarting of the JVM:
   -DPRECISE_SSL_RECOVERED_ID=<PREVIOUS_ID>
   The find the related instance ID, use the get-instance-id command, see Installing a new instance while keeping historical data from an old instance on page 82.

   ...