Linux local

En esta sección se describen los pasos para configurar Oracle Management Agent y desplegar los plugins de JMS en un host de Linux local mediante el script de instalación.

Requisitos:

Ejecute el script de instalación con sudo o acceso administrativo.

Nota

De forma predeterminada, la secuencia de comandos de instalación:

Cree o actualice el archivo de propiedades de Java Usage Tracker con una funcionalidad adicional para recopilar la propiedad user.name para una mejor identificación de las aplicaciones que se ejecutan en servidores de aplicaciones como WebLogic y Tomcat. Si no desea activar esta función, ejecute la secuencia de comandos de instalación con el argumento --enable-user-name=false. Puede modificar el archivo de propiedades de Java Usage Tracker en el futuro para agregar o eliminar user.name de la sección additionalProperties.
Desactive el modo Federal Information Processing Standards (FIPS) para los plugins.
El plugin lee la variable de entorno del sistema ENV_AGENT_PLUGIN_FIPS_APPROVED y, si se encuentra, activa el modo FIPS para los plugins. USGov relams. Para crear o modificar esta variable, ejecute el script de instalación con el argumento --enable-fips-mode=true.
Instale el agente con la frecuencia de telemetría predeterminada de MACS.

Ejecute el comando --help para ver la descripción de opciones como activar o desactivar el nombre de usuario, la configuración de proxy, FIPS, etc.

A continuación se muestran los parámetros opcionales junto con la descripción:


-u, --uninstall               Uninstall plug-ins, delete configuration files or restore originals from backups and exit.
-r, --reinstall               Uninstall plug-ins, delete configuration files or restore originals from backups and continue installation.
-h, --help                    Print usage message end exit.
--diagnostic                  Determines if prerequisite conditions are met on the host machine to allow for successful agent installation or upgradation, and plug-in deployment. 
                              Installation attempt will be skipped.
--enable-user-name            Generate usage tracker with additional functionality to collect the 'user.name' property for better identification 
                              of applications running on Application Servers like WebLogic and Tomcat servers. 
                              Default value is 'true'. 
--enable-fips-mode            Enable FIPS mode for plug-ins in USGov realms.
                              Format is --enable-fips-mode=true|false (for example, --enable-fips-mode=false).
                              Modify /etc/environment and create a line with ENV_AGENT_PLUGIN_FIPS_APPROVED=true or false.
                              Default value is false.
--install-management-agent    Installation of OMA on the OCI compute instance.                               
--uninstall-management-agent  Uninstallation of OMA on the OCI compute instance.                                
--reinstall-management-agent  Force OMA installation on the OCI compute instance and remove existing OMA.                               
--ignore-unsupported          The setup will proceed on an unsupported platform. 
                              Installation might be successful, but not all functionality might work as intended.
--proxy-host                  Add proxy host to curl commands, add or replace line 'ProxyHost = VALUE' in install key before Management Agent setup.
                              Format is --proxy-host="VALUE" (for example, --proxy-host="100.0.0.10").
                              Default is no proxy.
--proxy-port                  Add proxy port to curl commands, add or replace line 'ProxyPort = VALUE' in install key before Management Agent setup.
                              Format is --proxy-port="VALUE" (for example, --proxy-port="8050").
--proxy-user                  Add proxy user to curl commands, add or replace line 'ProxyUser = VALUE' in install key before Management Agent setup.
                              Format is --proxy-user="VALUE" (for example, --proxy-user="opc").
--proxy-password              Add proxy password to curl commands, add or replace line 'ProxyPassword = VALUE' in install key before Management Agent setup.
                              Format is --proxy-password="VALUE" (for example, --proxy-password="example").
--proxy-realm                 Add or replace line 'ProxyRealm = VALUE' in install key before Management  Agent setup.
                              Format is --proxy-realm="VALUE" (for example, --proxy-realm="OC1").
--use-agent-installer-path    Path to management agent installation file if it isn't in the same folder as the install script.
--use-java-path               Specify the Oracle Java 8 installation path for agent installation.  
                              If the path is not specified, the script will attempt to find a suitable Oracle Java 8 installation path from the file system. 
                              Format is --use-java-path={CUSTOM_PATH}(for example, --use-java-path=/usr/java/jdk1.8.0_361)).    
--use-agent-display-name      Specify the name to be displayed on the MACS console of your Management Agent.
                              If the name is not specified, the script will generate the name automatically.

Pasos

(Comprobación de diagnóstico opcional) Navegue hasta la carpeta en la que guardó el script de instalación y el software del agente de gestión. Ejecute el script con el siguiente comando:

$ sudo bash ./JMS_YourFleetName_linux.sh --diagnostic

Según el sistema operativo y el tipo de agente, los resultados serán similares a:

Fallo de diagnóstico:

======================================================================================================
Diagnostic Summary
======================================================================================================
Shell is supported? : Yes
User has sudo/root privileges? : Yes
Certified OS? : Yes
Meets minimum disk requirements? : Yes
Meets minimum memory requirements? : Yes
Able to reach OCI https://oracle.com endpoint? : Yes
Meets Java requirement? : Yes
Valid Management Agent installer? : No    
   Found 2 files with 'oracle.mgmt_agent*.rpm' pattern in /home/opc folder.    
   Please, run script test_linux.sh again with --use-agent-installer-path parameter.
Management Agent has been detected? : No
======================================================================================================
Diagnostics have failed. Please resolve all issues and run script test_linux.sh again.

El diagnóstico se ha realizado correctamente:

======================================================================================================
Diagnostic Summary
======================================================================================================
Shell is supported? : Yes
User has sudo/root privileges? : Yes
Certified OS? : Yes
Meets minimum disk requirements? : Yes
Meets minimum memory requirements? : Yes
Able to reach OCI https://oracle.com endpoint? : Yes
Meets Java requirement? : Yes
Valid Management Agent installer? : Yes
Existing Management Agent has been detected? : Yes
Existing Management Agent has JMS plugins? : Yes
Existing Management Agent can be upgraded? : Yes
======================================================================================================
Diagnostics have finished running and no error occurred.

Consulte Running Agent Installation Diagnostics para obtener la lista completa de preguntas con soluciones o recomendaciones.

Vaya a la carpeta donde guardó el script de instalación y el software del agente de gestión. Ejecute el script con el siguiente comando:
```
$ sudo bash ./JMS_YourFleetName_linux.sh
```
- Si la instalación se realiza correctamente, verá un mensaje similar al siguiente:
```
...
Management Agent installation has been completed.
Management Agent plugin 'Java Management Service' installation has been completed.
Management Agent plugin 'Java Usage Tracking' installation has been completed.
Management Agent was successfully registered using key YourFleetName (ocid1.managementagentinstallkey.oc1.iad.<ocid hash>).Assigned JMS Fleet is YourFleetName (ocid1.jmsfleet.oc1.iad.<ocid hash>).
```
- En caso de que el agente ya esté instalado, el script actualizará el software del agente a la última versión, si corresponde. Si los plugins de JMS aún no se han desplegado, despliegue Seguimiento de uso de Java y Java Management Service de forma manual, como se describe en la página Desplegar un plugin de servicio mediante la página Agentes. O bien, puede volver a instalar el agente junto con el despliegue del plugin JMS; ejecute el script con el parámetro --force.

(Opcional) Para verificar si el agente de gestión se está ejecutando, escriba:

$ sudo systemctl status mgmt_agent

Los resultados mostrarán:

mgmt_agent.service - mgmt_agent
   Loaded: loaded (/etc/systemd/system/mgmt_agent.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2022-08-24 07:05:38 GMT; 24s ago
  Process: 1772 ExecStart=/opt/oracle/mgmt_agent/agent_inst/bin/agentcore start sysd (code=exited, status=0/SUCCESS)
 Main PID: 1864 (wrapper)
   Memory: 414.6M
   CGroup: /system.slice/mgmt_agent.service
           ├─1864 /opt/oracle/mgmt_agent/agent_inst/bin/./wrapper /opt/oracle/mgmt_agent/agent_inst/bin/../config/wrapper.conf wrapper.syslog.ident=mgmt_agent wrapper.pidfile=/opt/oracle/mgmt_agent/agent_inst/bin/../log...
           └─2171 /usr/java/jdk1.8.0_301-amd64/bin/java -Dorg.tanukisoftware.wrapper.WrapperSimpleApp.maxStartMainWait=5 -Djava.security.egd=file:///dev/./urandom -XX:+HeapDumpOnOutOfMemoryError -Dpolyglot.engine.AllowE...

Aug 24 07:05:21 name-agent-stage systemd[1]: Starting mgmt_agent...
Aug 24 07:05:21 name-agent-stage agentcore[1772]: Removed stale pid file: /opt/oracle/mgmt_agent/agent_inst/bin/../log/mgmt_agent.pid
Aug 24 07:05:21 name-agent-stage agentcore[1772]: Starting mgmt_agent...
Aug 24 07:05:33 name-agent-stage agentcore[1772]: Waiting for mgmt_agent..............
Aug 24 07:05:34 name-agent-stage sudo[2752]: mgmt_agent : TTY=unknown ; PWD=/opt/oracle/mgmt_agent/agent_inst/bin ; USER=root ; ENV=ORACLE_CLOUD_AGENT_PLUGIN_COOKIE=<Cookie_ID> LOGDIR=/opt/or...
Aug 24 07:05:38 name-agent-stage systemd[1]: Started mgmt_agent.

También puede ver la consola para verificar si el agente de gestión se está ejecutando. Consulte Management Agent Console Overview para obtener más información.

Los archivos log se encuentran en el directorio /opt/oracle/mgmt_agent/plugins/jm/stateDir/log.

Documentación de Oracle Cloud Infrastructure

Linux local