Any other number, we will check for min and/or max length. Password length control equal to 0 means no restriction. Should you want to change this value you can do so by modifying -Xms and -Xmx parameters in acsera.sh (.bat) file.īear in mind that if you have installed CAMM as a Windows service and need to change the JVM Memory size, you need to change the size either by updating the Windows Registry or rerunning the createmanagerservice.bat utility with the new JVM parameters.Įxample A-2 User Password default is no length or complexity or expiration day limitation. In addition, acseraenv.sh(.bat) should have a pointer to the JDK used by CAMM:įor UNIX: JAVA_HOME=/home/oracle/em10g/j2sdk export JAVA_HOMEįor Windows: set JAVA_HOME=C:\oracle\em10g\j2sdkĬAMM is a Java application and runs in its own JVM. Only the files that are frequently customized will be described in this chapter.Īll the files in this directory should have these lines, pointing to the CAMM Installation location:įor UNIX: ACSERA_HOME=/home/CAMM export ACSERA_HOMEįor Windows: set ACSERA_HOME=C:\oracle\em10g\ To configure CAMM Server JVM parameters, e.g. To change the pointers to the location of Java Runtime Environment and CAMM installation directory (ACSERA_HOME) There are two main reasons why one would need to customize the content of the files in this directory: The /bin directory has all the executable files to start and stop CAMM, run deployer for Agent and CAMM EJB, run export utility. Do not modify these files.Ĭontains all the metadata definitions used for CAMM's needs.Ĭontains utility used to uninstall the CAMM. This directory is created once CAMM is up and running.Ĭontains internal base instrumentation configuration. Also logs indicating successful deployment of CAMM Agents can be found here. Has all the diagnostics records of CAMM performance metrics collection activities. Has all the libraries required for CAMM's proper functionality These components are deployed on the remote host (Web or Application servers) using deployer utility found in bin directory of CAMM package.Ĭontains minimum Java SDK sufficient to run CAMM Server. This directory is created once CAMM is up and running.Ĭontains agent libraries and configuration files, as well as CAMM EJB and CAMM Admin Web Application. Stores temporary images for J2EE applications that need to be monitored as well as the results of analysis and modeling of the J2EE application. Tomcat server where CAMM Web Application (GUI) is locatedĬontains all the executable files to start and stop CAMM, run deployer for Agent and CAMM EJB, run export utility.Ĭontains all the CAMM runtime configuration parameters that control execution logic, CAMM schemas enablement, CAMM GUI functionality, Service Level Objectives definition, export logic and many more. Table A-1 Directories in $CAMM_HOME Directory Directory
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |