Prerequisites

To use and run Deployit, your clients, server and target servers must fulfill the following prerequisites:

Client requirements:

A web browser (IE 7.0 or up, Firefox 3.0 or up, Safari 3.0 or up) compatible with and running Adobe Flash Player 9.0.115.0 and up.

Server requirements:

  • JDK 1.5 (Sun, IBM or Apple) or up
  • Linux with 2.6 kernel or up, AIX 5.3 or up, Windows 2008 Server
  • At least 2GB of internal memory, of which 256Mb should be allocated to the JVM.
  • A directory accessible to the Deployit installtion to host the Application Repository.
  • One of the following JDBC compatible databases:
    • Oracle 9i or up (JDBC driver not provided)
    • MySQL 5.0 or up (JDBC driver not provided)
    • HSQLDB (JDBC driver provided)
  • LDAP x.509 compliant registry for enabling group based security. If you are not interested in testing LDAP integration you can also use builtin security. See the user manual for details.

Expect to use a couple of GB's (Application Repository and database tablespace) with Personal Edition.

Target systems

The target systems (where you deploy to) should run Unix-compatible or Windows operating systems.

The target systems should be accessible by SSH, i.e. they should run an SSH2 server. The SSH2 server should be configured to allow SFTP access. For Windows systems Deployit has only been tested with WinSSHD.

Deployit will attempt to execute certain commands on the target systems under a specified user account, which therefore needs to have permissions to execute these commands. See the user guide for details.

Target Middleware

The target middleware needs to be set up so that the administrative interfaces of the target middleware can be accessed by running it on the machine on which the administrative server of the software is installed. Deployit does not support a setup in which the administrative client is installed on a different machine.

For WebSphere Application Server this means that Deployit will use SSH to log in to the machine on which the "deployment manager" is running and invoke wsadmin.sh there.

For WebLogic Server this means that Deployit will use SSH to log in to the machine on which the "admin server" is running and invoke wlst.sh there.