ODP node monitoring and maintenance Alexander Kolesnikov RIHMIWDC

VM startup order VM startup sequence after starting the ESXi server. Component startup order:

Regular works • Checking system logs of virtualization environment and operating system for failures

Important rules • Application server (JBoss, Tomcat) should only be run from a dedicated

Backup scheduler Component ID DB Frequency of backup Backup directory / dump db Many

Backup scheduler Every 12 hourly daily IS /opt/is/jboss 4. 2. 3. GA/server/default/conf/iserv/resources 14 00:

Backup scheduler SOI daily /opt/soi/jboss-5. 1. 0. GA 31 00: 20 PORTAL (jboss) daily

Backup. Configure client’s Action Command Install Xinetd yum install xinetd rsync Enable rsync in

Backup. Configure server Action Command Install Xinetd yum install xinetd rsync Enable rsync vi

Backup VM note! VM image backup is performed once. Subsequent backups should be made

Slides: 16

Download presentation

ODP node monitoring and maintenance Alexander Kolesnikov RIHMI-WDC, Russia 1

VM startup order VM startup sequence after starting the ESXi server. Component startup order: 1. Monitoring 2. Database 3. Service Bus 4. Integration Server 5. Data Provider 6. Portal 2

Regular works • Checking system logs of virtualization environment and operating system for failures and unauthorized access • Checking system logs of application servers for errors • Changing passwords of administrative and specialized users, virtualization environment and operating systems. 3

Important rules • Application server (JBoss, Tomcat) should only be run from a dedicated user rights • In case of database restart it is necessary to restart application servers for Portal and Service Bus components • Monitor the actuality of component backups. 4

Backup scheme 5

Backup scheduler Component ID DB Frequency of backup Backup directory / dump db Many versions Start Scheduler (GMT) daily jbossportal, juddi 31 22: 00 daily /opt/dp/jboss 4. 2. 3. GA/server/default/data/dpms /opt/dp/jboss 4. 2. 3. GA/server/default/conf/dpms/resour ces/*. xml 7 03: 30 weekly /opt/dp/jboss 4. 2. 3. GA/server/default/deploy/dpms. sar /opt/dp/jboss 4. 2. 3. GA/server/default/conf/dpms 4 Monday 02: 30 once /opt/dp/jboss-4. 2. 3. GA 2 ------ DP 6

Backup scheduler Every 12 hourly daily IS /opt/is/jboss 4. 2. 3. GA/server/default/conf/iserv/resources 14 00: 00 12: 00 /opt/is/jboss 4. 2. 3. GA/server/default/conf/iserv/log /opt/is/jboss 4. 2. 3. GA/server/default/conf/iserv/cache /opt/is/jboss 4. 2. 3. GA/server/default/conf/iserv/elements 7 01: 30 monthly /opt/is/jboss-4. 2. 3. GA/server/default/conf 2 First day of month 02: 40 once /opt/dp/jboss-4. 2. 3. GA 2 -----7

Backup scheduler SOI daily /opt/soi/jboss-5. 1. 0. GA 31 00: 20 PORTAL (jboss) daily /opt/portal/jboss-portal-2. 7. 2 31 00: 40 PORTAL (tomcat) daily /opt/portal/apache-tomcat-6. 0. 29 31 ------ 8

Backup. Configure client’s Action Command Install Xinetd yum install xinetd rsync Enable rsync in xinetd vi /etc/xinetd. d/rsync replace disable = yes to disable = no Download rsync. conf files in your component 9

Backup. Configure server Action Command Install Xinetd yum install xinetd rsync Enable rsync vi /etc/xinetd. d/rsync replace disable = yes to disable = no Download backup script Create a scheduler in the crontab –e Add scheduler's task 10 Save crontab file

Backup VM scheme 11

Backup VM note! VM image backup is performed once. Subsequent backups should be made after the global changes in the operating system or in case of software updates. In the case of a server failure, you can run the VM image on other ESXi host and continue your work 12

Monitoring scheme 13

Monitoring examples 14

Monitoring examples 15

Questions? 16