Introduction

What if you've so many J2EE environments that you'll want to industrialize your deployment process? Well, you'll look in the web, and you'll surely choose AutoDeploy form Build Process project. And you're right ;). Now that you can manage dozen of environments, which are connected to at last the same number of database instances, it will come to you that the monitoring of your ressources is not good enough.

That was basically what happended to me: 104 environments, each connected to an average of 4 Oracle database schema's... What a headache to find out what is the situation of your servers.

Displayed information

Summary:
  • Number of environments
  • Number of environments where database connection is missing
  • Number of databases
  • Number of schemas
  • Total size of all databases
Autodeploy extract:
  • Environment name
  • Used agent
  • Datasources connections settings
  • Database schema found indicator:
    IconDescription
    the corresponding database has not been found in databases list
    the database is also used by another environment
    the corresponding database has been found in databases list
Databases instances extract:
  • Datasource name (as configured)
  • Host name
  • Host port number
  • Database type
  • Database version
  • Encoding
  • Size
For each database, the list of tablespaces, where applicable:
  • Name
  • Status
  • Free space
  • Used space
  • Used percentage
For each database, the list of schemas, where applicable:
  • Name
  • Description (Meta Information)
  • Creation date
  • Status
  • Default tablespace
  • Temporary tablespace
  • Size
  • Export control where
    IconDescription
    Update status
    Launch export
    Dump running
    Dump export launch blocked. You may click on the icon to know the reason
    Export successful (but always check the log...)
    Export failed
    Download log
    Download dump
    Download MD5Sum of the dump file
  • Connected environment found indicator:
    IconDescription
    no connected environments has been found in environments list
    this database have been definec has not linkable to a AD environment (Meta Information)
    a connected environments has been found in environments list

Supported databases

Currently, only Oracle is supported. I plan to support MySQL, but any contribution is welcomed ;)

Tools

AutoDeploy environments links as RSS

The application generates a RSS stream using weblinks defined in AutoDeploy environments. To display it, simply click on the AD RSS icon in the tool bar.

Configuration file generation

You can download dynamicaly generated configuration files for:
IconDescription
Oracle SQL*Plus

Configuration

Enabling database monitoring

The databases to be monitored just have to be defined as datasources in the web container, with a user who have enough privileges (system for Oracle, root for MySQL,...).

Allowing access to the monitoring page

The user simply have to exist in the LDAP used for authentication. Once authenticated, it will be automatically added as a user for this application, but with no rights.

Allowing dump export for a user

There is no front-end for this configuration yet, so you'll have to do it directly in integration database. First, get the user id using the following query: 
select USR_ID from DT_USER where USR_LOGIN = 'user_login'
Then defined this user as having rights to execute exports using the following insert: 
insert into ASS_USR_RGT (USR_ID, RGT_ID) values (user_id, 'DUMP_EXPORT')

Allowing database meta-information for a user

Get the user id as specified in the previous section. Then defined this user as having rights to update database meta-information using the following insert: 
insert into ASS_USR_RGT (USR_ID, RGT_ID) values (user_id, 'META_DB')