macOS local

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

Requisitos:

Ejecute el script de instalación con sudo o acceso administrativo y otorgue el permiso Full Disk Access.

Nota

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

Genere un rastreador de uso con 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, actualice el parámetro --enable-user-name=false en el script de instalación. 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. Para activar el modo FIPS en los relams USGov, actualice el parámetro --enable-fips-mode=true en la secuencia de comandos de instalación.
Instale el agente con Frecuencia de telemetría inferior de JMS.

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.

Los siguientes son 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 in Application Servers like Weblogic and Tomcat servers.
                            If you want to disable this feature, update the parameter --enable-user-name=false in the installation script.
                            Alternatively, modify /Library/Application Support/Oracle/Java/usagetracker.properties and add or remove 'user.name' in 				    'additionalProperties'.
                            Default value is true.
--enable-fips-mode          Enable FIPS mode for plugins in USGov realms.
                            Format is --enable-fips-mode=true|false (for example, --enable-fips-mode=false).
                            Modify /etc/bashrc and create a line with ENV_AGENT_PLUGIN_FIPS_APPROVED=true or false.
                            Without this parameter script won't change anything in /etc/bashrc file.
--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. All proxy parameters are optional.
--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-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").
--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").
--use-agent-installer-path  Use this file to setup Management Agent. Optional parameter.
                            If exists, script won't try to find installation files in current folder.
--use-java-path             Use the Java Installation on this path to set up Management Agent. Optional parameter
                            Format is --use-java-path="JAVA_PATH" 
                            (for example, --use-java-path=/Library/Java/JavaVirtualMachines/jdk1.8.0361.jdk/Contents/Home).
--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_macos.sh --diagnostic

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

Fallo de diagnóstico:

======================================================================================================
Diagnostic Summary
======================================================================================================
User has sudo/root privileges? : Yes
Certified OS? : Yes
Meets minimum disk requirements? : Yes
Meets minimum memory requirements? : Yes
Able to reach OCI endpoint? : Yes
Certificate verification has been passed? : Yes
Is clock sync with OCI platform? : Yes
Available Java for agent installation ? : Yes
Management Agent installer available? : No
	Script JMS_YourFleetName_macos.sh can't find the Management Agent installer /kkk.
	Check if the path /kkk exists and check the '--use-agent-installer-path' parameter.
Existing Management Agent has been detected? : No
================================================================================
Diagnostics have failed. Please resolve all issues and run script JMS_YourFleetName_macos.sh again.
Please refer troubleshooting guide https://docs.oracle.com/en-us/iaas/jms/doc/troubleshooting.html for more details.

A copy of this installation log can be found at /Library/Oracle/JMSInstallScript/JMSInstallScriptLogs-<date>.log

El diagnóstico se ha realizado correctamente:

======================================================================================================
Diagnostic Summary
======================================================================================================
User has sudo/root privileges? : Yes
Meets minimum disk requirements? : Yes
Meets minimum memory requirements? : Yes
Able to reach OCI endpoint? : Yes
Certificate verification has been passed? : Yes
Is clock sync with OCI platform? : Yes
Existing Management Agent has been detected? : No
Available Java for agent installation ? : Yes
Management Agent installer available? : Yes
======================================================================================================
Diagnostics have finished running and no error occurred.

Consulte Running Agent Installation Diagnostics para obtener la lista completa de criterios comprobados durante el diagnóstico, junto con soluciones o recomendaciones.

Navegue hasta 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_macos.sh
```
- Si la instalación se ha realizado correctamente, verá un mensaje similar al siguiente:
```
...
Management Agent installation has been completed with 'Java Usage Tracking service plugin (Service.plugin.jms)'
JMS basic features will be enabled on this instance.
Management Agent installation has been completed with 'Java Management service plugin (Service.plugin.jm)'
JMS advanced features can be enabled on this instance.
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 aún no se han desplegado los plugins de JMS, despliegue los plugins de Seguimiento de Uso de Java y Java Management Service manualmente, como se describe en Despliegue un plugin de servicio con la página Agentes. O bien, puede volver a instalar el agente junto con el despliegue del plugin de JMS; ejecute el script con el parámetro --force.
(Opcional) Para verificar si el agente de gestión se está ejecutando, escriba:
```
$ sudo launchctl print system/com.oracle.macs.agent.mgmt_agent | grep state
```
Los resultados mostrarán:
```
state = running
```
También puede ver la consola para verificar si el agente de gestión se está ejecutando. Consulte Visión general de la consola de Management Agent para obtener más información.

Los archivos log se encuentran en el directorio /Library/Oracle/mgmt_agent/plugins/jm/stateDir/log.

Documentación de Oracle Cloud Infrastructure

macOS local