Chat now with support
Chat with Support

Foglight for Java EE Technologies 5.9.9 - Installation Guide

Install and Configure Foglight for Java EE Technologies Integrate with JBoss Integrate with Apache Tomcat Integrate with WebLogic Domain Startup Scripts Integrate with WebSphere Integrate with Oracle AS Create a Generic Installation for Manual Java EE Agent Integration Manage Java EE Agent Installations, Integrations, and Configurations Managing Java EE Agent Configurations Java EE Installation Management Java EE Integration Configuration FAQ and Troubleshooting Manual Application Server Integrations AppendixB: Managing Permissions for the Java EE Integration Agent Appendix A: Java EE Application Methods

Modifying the WebSphere 6.x and 7.x startup scripts

Use the steps in this section to modify the WebSphere 6.x and 7.x startup scripts.
* 
NOTE: The following procedures are not required if you are starting your servers, Node agent, or Deployment Manager using Windows services.
Before you begin
Review the following exceptions before you configure your server.
Exception list
•
If you want to set pre-instrumentor options specific to the JVM you are running:
Set the environment variable QUEST_PREINST_OPTS with the desired VM options. The environment variable QUEST_PREINST_OPTS is passed to the Java EE agent pre-instrumentor script.
For example, to set the memory used for the pre-instrumentor to 256MB, specify the following:
Windows:
QUEST_PREINST_OPTS=-Xms256m -Xmx256m
Unix:
QUEST_PREINST_OPTS=”-Xms256m -Xmx256m”
Modifying WebSphere 6.x or 7.x startup scripts
Complete the following steps to modify a WebSphere 6.x and 7.x startup script.
To modify the WebSphere 6.x or 7.x startup scripts:
1
Locate your profile-specific startServer, startNode, or startManager script. Save a backup copy before continuing.
2
Open your profile-specific startServer, startNode, or startManager script. Before the call to the WebSphere Installation startServer, startNode, or startManager script, add the following environment variable as appropriate:
Windows:
a
In startServer add:
set QUEST_JAVA_ENV_OPTS=WEBSPHERE:SERVER
b
In startNode add:
set QUEST_JAVA_ENV_OPTS=WEBSPHERE:NODEAGENT
c
In startManager add:
set QUEST_JAVA_ENV_OPTS=WEBSPHERE:DMGR
Unix:
a
In startServer add:
QUEST_JAVA_ENV_OPTS=WEBSPHERE:SERVER
export QUEST_JAVA_ENV_OPTS
b
In startNode add:
QUEST_JAVA_ENV_OPTS=WEBSPHERE:NODEAGENT
export QUEST_JAVA_ENV_OPTS
c
In startManager add:
QUEST_JAVA_ENV_OPTS=WEBSPHERE:DMGR
export QUEST_JAVA_ENV_OPTS
3
Restart your application server. See, Restarting modified WebSphere 6.x or 7.x servers.

Restarting modified WebSphere 6.x or 7.x servers

After you have modified the startup script, restart the WebSphere® 6.x or 7.x server.
To start the WebSphere 6.x or 7.x modified server:
1
If it is not already running, start the Foglight Management Server.
2
Stop and restart the WebSphere server using the instructions for the server type you modified:
•
If you are using a standalone WebSphere server, stop the server and restart it with the modified script or the new Windows Service.
•
When starting WebSphere 6 servers managed by a WebSphere Deployment Manager, stop the WebSphere node agent and restart the node agent with the modified script or with the new Windows Service. Restart any managed WebSphere Application Server instances after restarting the modified WebSphere node agent.
•
When starting a standalone WebSphere 7 Server managed by a WebSphere Admin Agent, stop the WebSphere Admin Agent and restart the Admin Agent with the modified script or with the new Windows Service. Restart any managed WebSphere Application Server instances after restarting the modified WebSphere Admin Agent.
* 
CAUTION: For any server with a corresponding Windows service: Attempts to start a server by using a startup script may launch a Windows service instead. If the startup script is instrumented with the Foglight for Java EE Technologies, then the resulting WebSphere process is instrumented as well. Otherwise, the integration properties of the Service are used. This release changes the behavior of services launched as a result of a start script invocation.
* 
CAUTION: Foglight starts a Java EE agent for each instrumented server. When the Java EE agent connects to the Management Server, the Management Server console displays a message to confirm that a Java EE agent has connected. For example: INFO agent licenses assigned; Type: websphere, Host: <hostName>, CPUs: 1; CPU licenses in use: INFO Accepted DCE connection from agent "server1 (WebSphere)" (WebSphere 6.X). The log file for the Java EE agent also contains an INFO message stating that it has connected to the Management Server.
 

AppendixB: Managing Permissions for the Java EE Integration Agent

To manually adjust the permissions for the Java EE Integration Agent, use the Foglight for Java EE Technologies Agent Properties page.
Before you make any changes, review the following topics:
•
Managing permissions on remote filesystems
•
Windows Services permissions
•
Permissions required by the application server user
To edit Java EE Integration Agent permissions:
1
On the navigation panel, under Dashboards, click Administration > Agents > Agent Properties.
2
On the Agent Properties dashboard, expand the ApplicationServers Namespace > Type group.
3
Click JavaIntegrator. The Properties page for the Java EE Integration Agent opens.
4
Set the permissions as necessary and click Save.

Managing permissions on remote filesystems

Before creating and activating an instance of the Java EE Integration Agent on a remote host, the user running the Agent Manager process must have permission to create the Installation directory (DEPLOYMENT_DIRECTORY).
Before submitting an integration task to a Java EE Integration Agent, the Java EE Integration Agent must be granted permission to make the necessary changes to application server files and to create backup copies of the files being changed. The following permissions must be granted to the user running the Agent Manager process (for the application server being integrated):
Table 8. User permissions required.
Remote File System directory
Directory/App Server file
Required permission
DEPLOYMENT_DIRECTORY
.
(managed)
..
ugo+rwx
(JBoss)
JBOSS_HOME/bin
.
ugo+rwx
standlone.bat, domain.bat , run.bat
ugo+rw
standalone.sh, domain.sh, run.sh
(Tomcat)
CATALINA_HOME/bin
.
ugo+rwx
catalina.bat, catalina.sh
ugo+rw
(WebLogic)
WL_HOME/server/bin
.
ugo+rwx
startNodeManager.cmd, startManagedWebLogic.cmd, startWLS.cmd
ugo+rw
startNodeManager.sh, startManagedWebLogic.sh, startWLS.sh
(WebLogic)
DOMAIN_HOME/common/bin
.
ugo+rwx
startWebLogic.cmd, startWebLogic.sh
ugo+rw
(WebSphere)
PROFILE_HOME/bin
.
ugo+rwx
startServer.bat, startNode.bat, startManager.bat, setupCmdLine.bat
ugo+rw
startServer.sh, startNode.sh, startManager.sh, setupCmdLine.sh
(WebSphere)
PROFILE_HOME/properties
.
ugo+rwx
server.policy
ugo+rw
(WebSphere)
WAS_HOME/bin
.
ugo+rwx
setupCmdLine.bat
ugo+rw
setupCmdLine.sh,
startServer.sh,
startNode.sh,
startManager.sh,
If the Agent Manager and Application Server processes use the same user, the "g" and "o" permissions can be omitted.
If the Agent Manager user is in the same group as the Application Server files being modified, the "u" and "o" can be omitted.
If the Agent Manager is not the same as the Application Server user, or in the same group, then the "o" must be included.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating