Chatta subito con l'assistenza
Chat con il supporto

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

Windows Services permissions

For integration of Windows Services, the Agent Manager user requires permission to run the regedit.exe executable in export or import modes on one or more registry keys, under the HKEY_LOCAL_MACHINE hive.

Permissions required by the application server user

The Java EE Integration Agent automatically grants permissions on the files and directories within the DEPLOYMENT_DIRECTORY to be readable by any other user on the remote filesystem. By default, only users in the same group as the Agent Manager (and the Agent Manager user itself) can create files within the DEPLOYMENT_DIRECTORY.
config, lib, scripts, and their subdirectories within versioned homes
All parent directories of DEPLOYMENT_DIRECTORY created by the Agent Manager
All files within config and lib and their subdirectories
By default, stock scripts are not set executable as they are sourced instead of run. If manual execution of pre-instrumentor.sh is required, it may be provided as an argument to /bin/sh instead of changing the permissions for this category.
Non-customized copies of integrate.cmd, integrate.sh
Files within versioned scripts directory
bootstrap, logs and state sub-directories
config file parent directories (except config, which is created using stock directory permissions)
DEPLOYMENT_DIRECTORY/exports (this is the WORKING_SUBDIR)
Agent-local config files (agent.config, log.config, agenttype.config)
The setuid bit can be set on script files to have the launched process take on the user ID of the script file itself. This ability is not needed in stock integrations.
The setgid bit can be set on script files and directories. When set on script files, the effect is similar to the setuid bit, except the launched process takes on the group ID of the script file, instead of the user ID. When set on a directory, the setgid bit results in files created in that directory having the same group ownership as the directory itself, rather than the group of the user who creates the file. By default, the setgid bit is set on Dynamic Directories, so that the Java EE Integration Agent can maintain these directories regardless of which user creates files within them.
The sticky bit can be used on directories with other write permission to prevent a user from deleting another user’s file.

Appendix A: Java EE Application Methods

Full detail instrumentation level

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione