Onboarding
There is a wide variety of systems, databases, and applications that can be monitored by IT-Conductor.
Each system has its own layer of security and unique user requirements that must be met prior to onboarding said system on IT-Conductor.
- IT-Conductor tenant registration including organization, sites, users (administrator, non-administration), and Single Sign-On (SSO). Register here.
- VM Provisioning of the IT-Conductor Gateway
- 4 vCPU, 16 GB RAM, 30 GB Disk space
- OS: SUSE SLES/RHEL
- Network
- The IT-Conductor Gateway VM should have outbound internet access.
- The IT-Conductor Gateway VM should be in the same network as the systems to be monitored, and the firewall should be open between the IT-Conductor VM and the systems to be monitored.
- Add Monitoring System
- Initial Configuration
Category | Component | Security | SAP Transport | Configuration |
---|---|---|---|---|
Application | SAP ABAP | |||
Application | SAP J2EE/JAVA | |||
Database | SAP HANA | N/A | ||
Database | SAP ASE | Create a dedicated ASE monitoring user with the "mon_role" role. | N/A | |
Database | MaxDB | Login to the SQLcl with your SYSDBA/DBADNMIN. | N/A | |
Database | Oracle | Create Oracle user with the "create_session" and "oem_monitoring" roles. | N/A | |
OS | Linux | N/A | ||
OS | Windows | N/A | ||
OS | SAP HostAgent | N/A | ||
Infrastructure | Azure | N/A | ||
Infrastructure | AWS | N/A | N/A | |
Automation Scenario | SAP Transport Automation | N/A | ||
Automation Scenario | End-to-End SAP System Refresh | N/A | N/A | |
Automation Scenario | Start/Stop Automation | N/A | N/A |
Last modified 4mo ago