Este documento describe los pasos para instalar el service manager de Mysql Enterprise Monitor en un sistema Linux. Incluye verificar los requisitos del usuario mysql, crear el directorio de instalación, ejecutar el instalador, y configurar la base de datos y usuarios del service manager.
Using the new IBM ODBC Driver for Notes/Domino 9.0Mat Newman
Steps through installing and configuring the new IBM ODBC driver for Notes/Domino 9 (formerly Notes SQL driver).
This demonstration utilises Microsoft Windows 8 as the Operating System and OpenOffice to test the configured connection.
Using the new IBM ODBC Driver for Notes/Domino 9.0Mat Newman
Steps through installing and configuring the new IBM ODBC driver for Notes/Domino 9 (formerly Notes SQL driver).
This demonstration utilises Microsoft Windows 8 as the Operating System and OpenOffice to test the configured connection.
15 Troubleshooting Tips and Tricks for database 21c - OGBEMEA KSAOUGSandesh Rao
This session will focus on 15 troubleshooting tips and tricks for DBA’s covering tools from the Oracle Autonomous Health Framework (AHF) like Trace file Analyzer (TFA) to collect , organize and analyze log data , Exachk and orachk to perform mass best practices analysis and automation , Cluster Health Advisor to debug node evictions and calibrate the framework , OSWatcher and its analysis engine , oratop for pinpointing performance issues and many others to make one feel like a rockstar DBA
Upgrade to IBM z/OS V2.4 technical actionsMarna Walle
Yes, "upgrade" is the new name for these traditional "migration" sessions! This is part one of a two-part session that will be of interest to System Programmers and their managers who are upgrading to z/OS 2.4 from either z/OS 2.2 or 2.3. It is strongly recommended that you review sessions for a complete upgrade picture.
The general availability date for z/OS V2.4 was September 30, 2019.
SAP Business One Integration Problems and Solutions - DI server DI API B1WSAPPSeCONNECT
During the Process of Upgrading and Configuring the Server you may find multiple Issues, So in this Presentation we have describe some common SAP Business One Integration Problems & their Solutions in DI Server, DI API & B1WS. If you faced any problem you can check its detail in this blog. http://bit.ly/b1-connect-problems
Oracle Enterprise Manager Seven Robust Features to Put in Action finalDatavail
Oracle Enterprise Manager (OEM) brings your Oracle deployments together in a single management, monitoring, and automation dashboard. Oracle developed this solution, so it offers deep integration with many of its technologies. The ease of integration, coupled with the support of both on-premise and cloud-based Oracle databases, allows it to fit into many enterprise infrastructures. Oracle Enterprise Manager can also monitor and manage non-Oracle databases, making it a cost-effective and central tool to manage IT environments with a mix of database platforms.
The single point of control is appealing for complex enterprise infrastructures, especially when they’re heavily invested in Oracle technologies. Out-of-the-box monitoring and reporting templates cover many common use cases, and simplifies the configuration of management automation for databases, applications, and more.
Watch the webinar to see a brief history of OEM and a deep dive into seven robust features organizations should consider implementing:
15 Troubleshooting Tips and Tricks for database 21c - OGBEMEA KSAOUGSandesh Rao
This session will focus on 15 troubleshooting tips and tricks for DBA’s covering tools from the Oracle Autonomous Health Framework (AHF) like Trace file Analyzer (TFA) to collect , organize and analyze log data , Exachk and orachk to perform mass best practices analysis and automation , Cluster Health Advisor to debug node evictions and calibrate the framework , OSWatcher and its analysis engine , oratop for pinpointing performance issues and many others to make one feel like a rockstar DBA
Upgrade to IBM z/OS V2.4 technical actionsMarna Walle
Yes, "upgrade" is the new name for these traditional "migration" sessions! This is part one of a two-part session that will be of interest to System Programmers and their managers who are upgrading to z/OS 2.4 from either z/OS 2.2 or 2.3. It is strongly recommended that you review sessions for a complete upgrade picture.
The general availability date for z/OS V2.4 was September 30, 2019.
SAP Business One Integration Problems and Solutions - DI server DI API B1WSAPPSeCONNECT
During the Process of Upgrading and Configuring the Server you may find multiple Issues, So in this Presentation we have describe some common SAP Business One Integration Problems & their Solutions in DI Server, DI API & B1WS. If you faced any problem you can check its detail in this blog. http://bit.ly/b1-connect-problems
Oracle Enterprise Manager Seven Robust Features to Put in Action finalDatavail
Oracle Enterprise Manager (OEM) brings your Oracle deployments together in a single management, monitoring, and automation dashboard. Oracle developed this solution, so it offers deep integration with many of its technologies. The ease of integration, coupled with the support of both on-premise and cloud-based Oracle databases, allows it to fit into many enterprise infrastructures. Oracle Enterprise Manager can also monitor and manage non-Oracle databases, making it a cost-effective and central tool to manage IT environments with a mix of database platforms.
The single point of control is appealing for complex enterprise infrastructures, especially when they’re heavily invested in Oracle technologies. Out-of-the-box monitoring and reporting templates cover many common use cases, and simplifies the configuration of management automation for databases, applications, and more.
Watch the webinar to see a brief history of OEM and a deep dive into seven robust features organizations should consider implementing:
Instalación service manager (mysql enterprise monitor)
1. Instalación del service manager (mysql enterprise monitor)
Mysql Enterprise tiene dos componentes principales el agente el encargado de recopilar la
información de la instancia de mysql y el service manager que el encargado de recopilar la
información que envía cada agente. A continuación se detalla el procedimiento para la instalación
del service manager en un sistema Linux
Requerimientos.
Requerimientos minimos:
2 or more CPU cores
2 or more GB of RAM
Disk I/O subsystem applicable for a write-intensive database installation
Requerimientos Recomendados (si monitorea 100 o mas Servidores Mysql)
4 or more CPU cores
8 or more GB of RAM
Disk I/O subsystem applicable for a write-intensive database installation (RAID 10, RAID 0+1)
Especificación de la máquina del ejemplo:
Máquina Virtual Oracle Virtualbox 4.3.8
S.O Host: Windows 7 SP1
S.O Guest: Debian 7
Paso 1: Validación del shell y directorio Home del usuario mysql
El usuario mysql debe existir en la maquina además de contar con una Shell y un directorio home
validación del Shell
Ejecutar (Como root): getent passwd mysql | cut -d: -f7
La salida debe ser:/bin/bash
Validación del directorio
Ejecutar (Como root): getent passwd mysql | cut -d: -f
La salida debe ser diferente a vacía (ruta del home de mysql)
Si alguna de las salidas es vacía se debe corregir de la siguiente manera:
2. Se debe detener todos los mysql que se estén ejecutando (comúnmente los scripts de
control de mysql se encuentran en “/etc/init.d” , ejecutar algo similar a: “/etc/init.d/mysql
stop”
Asignar Shell
Ejecutar (Como root): usermod -s /bin/bash mysql
Asignar home
Ejecutar (Como root): usermod -d /opt/mysql mysql
Paso 2: Crear directorio donde se instalara el service manager
El directorio de instalación pude ubicarse en cualquier ruta.
Crear Directorio de Instalación (para el presente ejemplo /opt/mysql/service-manager)
Ejecutar : mkdir -p /opt/mysql/service-manager
Paso 3: Asignar propiedad del directorio de instalacion a mysql
Ejecutar (Como root): chown -R mysql:mysql /opt/mysql
Paso 4: Cambiar Usuario a mysql
Ejecutar: su - mysql
Paso 5: Instalacion del Service manager
Se debe haber copiado los instaladores a la maquina, y luego de ubicarse en el directorio de
instalacion
Ejecutar: ./mysqlmonitor-2.3.15.2205-linux-x86_64-installer.bin
Las siguientes son las instrucciones del instalador:
o Selección de Idioma (el presente ejemplo utiliza ingles)
3. o Informacion de la instalcion
Se muestra infomracion para del proceso de instalacion simplemente dar <Enter>
o Bienvenida y directorio de Instalacion
se ingresa el directorio que creamos anteriormente para el presente ejemplo:
/opt/mysql/service-manager
o Puertos para tomcat y SSL
El service-manager funciona sobre un tomcat para tal caso se solicitan los puertos
de escucha del servidor, para el presente ejemplo se usan los siguiente puertos :
Tomcat Server Port: 8080
Tomcat Shutdown Port: 8085
Tomcat SSL Port: 8443
Y además no se utiliza SSL.
o Base de datos para el service-manager
El service-manager necesita una base de datos para el funcionamiento, se puede
utilizar una ya existente o crear una base de datos independiente, para el presente
ejercicio se creara una independiente.
o Configuración de la base de datos del service-manager
El instalador solicitara los parámetros de la base datos para el presente ejercicio
se utilizara los siguientes:
4. Repository Username: service_manager
MySQL Database Port: 13306
Use SSL when connecting to the database: n
o Confirmación de instalación:
Se confirma que se desea continuar e inicia el proceso de instalación.
o Instalación y Post instalación
Se inicia el proceso de instalación
Se muestra información de la instalación y se presiona enter para proseguir
El instalador pregunta si se desea visualizar el archivo léeme, para el presente
ejemplo se indica que no
Finalizado muestra la URL para el acceso al service-manager, se presiona enter y
finaliza la instalación
5. Paso 6: Configuración Enterprise Dashboard
Se ingresa a un navegador a la url:port de intalacion del Service-Manager.
Creación del usuario Manager
El “Manager User” es el usuario administrador del dashboard se ingresan los datos para el
presente ejemplo:
User: root
Password: 1234567
Creación del usuario Agent
Es el usuario con el cual cada instancia del agente de monitoreo se conecta al Enterprise
manager. Cuando se instale cada agente se debe ingresar este usuario. Para el presente
ejemplo:
User: agent
Password: 1234567
Advisors
En la sección Advisors (parte inferior de la página web) se debe seleccionar el archivo .jar
que contiene los advisor por defecto.
Finalizados los pasos se carga el index del Enterprise Dashboard.