Free 30 Day Trial
Find the root-cause of your cloud, hybrid-cloudor on-prem performance issues
Configuring Oracle WebLogic Application Server 9.2
The eG agent package contains a web archive file called egurkha9x.war. On Unix environments, this file will be available in the /opt/egurkha/lib location. On Windows environment, this file will be available in the <EG_HOME_DIR>\lib directory. This file has to be installed on the WebLogic server ver. 9 (and above), which has to be monitored. Prior to deploying this war file, make sure that you follow the steps below:
Next, follow the steps given below to deploy the war file:
Next, go to the following URL: http://<WebLogic_server_IP>:<WebLogicPort>/.
Now, an authentication dialog (see Figure 2) that requires a username and password, will appear. Specify the user name and password of the WebLogic administrator to login.
Upon successful authentication, the following WebLogic 9.2 Administration console will appear (see Figure 3).
From the Domain Structure section in the left panel of Figure 3, choose the Deployments node. A Summary of Deployments follows (see Figure 4), which lists all the applications that pre-exist on the WebLogic server (see the right panel).
To add a new application, you first need to change to the Edit mode. To achieve this, click on the Lock & Edit button under the Change Center section in the left panel of Figure 4. Following which, the Install button in the Deployments section of the right panel, gets enabled (see Figure 5).
To begin application deployment, click on the enabled Install button in the right panel of Figure 5 above. Next, using the slew of screens that appear one after another, browse for and specify the full path to the egurkha.war file (path: <EG_INSTALL_DIR>\agent\lib) to be deployed (see Figure 6, Figure 7, Figure 8, and Figure 9.
By default, the egurkha.war file will be searched for in the local disk of the system from which the browser is launched. Therefore, if you are trying to access the WebLogic console from a system that does not host an eG agent, then, before attempting to deploy the egurkha.war file, do the following:
Select the Install this deployment as an application option in Figure 10 that appears next, and then, click the Next button to move on.
Provide a Name for the new application in Figure 11. By default, egurkha will be displayed therein. Then, click on the Next button to proceed.
To complete the application deployment, click on the Finish button in Figure 12.
The existing configuration settings for the new application is then made available for review. To save the settings, click on the Save button in Figure 13.
Figure 14 then appears, which lists the applications that have been deployed on the WebLogic server. If the egurkha application appears in the list, it is indicative of the successful installation of the egurkha.war file.
To ensure that the changes are saved, click on the Activate Changes button under the Change Center section in the left panel of Figure 14. Upon successful change updation, a message to that effect appears at the top of the right panel, as depicted by Figure 15.
Now, proceed to start the application. To do so, first, click on the check box that corresponds to the egurkha entry in the Deployments list, click on the Start button above, and choose the Servicing all requests option from the drop-down menu (see Figure 16).
Click the Yes button in Figure 17 to confirm starting.
If the application starts successfully, then a message to that effect appears, as depicted by the right panel of Figure 18.