2 System Requirements

This chapter details the system requirements to install and effectively use Application Configuration Console. System requirements are deemed to be the minimum and recommended software and hardware specifications, including all third-party applications required to support Application Configuration Console.

2.1 Application Configuration Console Server

Table 2-1 lists the system requirements necessary to support Application Configuration Console's Core Server, also known as the primary server, and the tracking and Web Reports servers, also known as the secondary servers. An installation of the Core Server includes separate deployments of the primary server and secondary servers. These secondary servers are candidates for redeployment to other instances of a Tomcat JVM on separate hosts, in which case Table 2-2 lists the system requirements necessary to support them.

Table 2-1 System Requirements for the Core Server

Core Server (Primary Server)
Operating System	Windows Server 2003	Red Hat Enterprise Linux (4.0, 5.0) SUSE Linux Enterprise Server (10)	Solaris (9, 10)
Processor	3 GHz dual processor		UltraSPARC IV or greater, 1 GHz dual processor
Installed Memory	2 GB (minimum) 3 GB (recommended)
Available Memory	2 GB (minimum) 2.8 GB (recommended)
Disk Space	Minimum 40 GB (500 MB for installation, plus space for repository)
Third-Party Software	See Table 2-5

2.2 Application Configuration Console Secondary Servers

Redeployment of secondary servers, which is optional, has implications for performance and scalability. It reduces the load on the primary server so that response times are faster for other tasks, such as compare and provision operations. You can also deploy multiple secondary tracking servers, based on the original tracking server deployment, to improve throughput of tracking operations.

Table 2-2 lists the system requirements necessary to support secondary server instances. The requirements listed in Table 1 are sufficient to support both the primary and secondary servers.

Table 2-2 System Requirements for the Secondary Servers

Secondary Servers
Operating System	Windows Server 2003	Red Hat Enterprise Linux (4.0, 5.0) SUSE Linux Enterprise Server (10)	Solaris (9, 10)
Processor	3 GHz dual processor		UltraSPARC IV or greater, 1 GHz dual processor
Installed Memory	2 GB (minimum) 3 GB (recommended)
Available Memory	2 GB (minimum) 2.8 GB (recommended)
Disk Space	500 MB
Third-Party Software	See Table 2-5
Additional Requirements	OS must match the primary server OS Secondary server directory structure must match that of the primary server (for example: `/user/oracle/oacc/server`)

2.3 Oracle Database Server

Table 2-3 lists the system requirements necessary to support the Oracle database server needed to run Application Configuration Console.

Table 2-3 System Requirements for the Oracle Database Server

Oracle Database Server
Supported RDBMS versions	10g (10.2.0.3 - Standard or Enterprise Edition) 11g recommended (11.1.0.1 - Standard or Enterprise Edition)
Operating System	See Oracle documentation
Processor	3 GHz dual processor
Installed Memory	2 GB (minimum) 3 GB (recommended)
Available Memory	1.8 GB (minimum) 2.8 GB (recommended
Disk Space	5 GB (minimum) 10 GB (recommended)
Oracle Settings	SGA settings should be as follows: Shared pool-512MB Buffer cache-512MB Large pool-8MB Java pool-256MB minimum; 1GB recommended Aggregate PGA target-512MB
Additional Requirements	The Oracle installation must have embedded Java support (JServer option); this is built in to 11g.

2.4 Application Configuration Console Client

Table 2-4 lists the system requirements necessary to support the Client.

Table 2-4 System Requirements for the Client

Application Configuration Console Client
Operating System	Windows XP Professional Windows 2003 Vista
Processor	2 GHz
Installed Memory	1 GB (minimum) 1.5 GB (recommended)
Available Memory	768 MB (minimum) 1 GB (recommended
Disk Space	300 MB
Third-party Software	See Table 2-5

2.5 Third-Party Software

Table 2-5 lists the third-party software requirements for Application Configuration Console.

Table 2-5 Application Configuration Console Third-Party Software Requirements

This Component	Requires These Third-Party Components
*And all subsequent patch releases issued for 1.6.0
Primary Server	Sun Microsystems JDK 1.6.0_01* Directory service (the Core Server must be able to connect to a directory service); LDAP 2.0 or later, or Microsoft Windows Active Directory 2000 or 2003 Mail Server (Core Server must be able to connect to the mail server) Apache Tomcat 6.0.14 (embedded with the software) SVN 1.4.4 server and repository (embedded with the software, except for the Solaris version) Java CIFS Client Library (JCIFS) Version 1.3.12 if you want UNC Support Business Intelligence and Reporting Tools (BIRT) Runtime Version 2.5.0 (embedded with Web Reports)
Secondary Servers	If you follow the instructions in Appendix D on redeploying secondary servers, everything you need in terms of third-party software will be in place in the copied directory structure. The redeployments call in to services such as SVN, LDAP or AD, and e-mail, so there is no physical requirement on the secondary server host to support these services.
Client	Sun Microsystems JDK1.6.0_01* Eclipse Runtime Platform 3.3.x (embedded with the software) Microsoft Internet Explorer 7 or 8 (for Web Reports) Mozilla Firefox 2 or 3 (for Web Reports)
WebLogic Automation Module	WebLogic Server (8, 9, or 10) installed on the Core Server
WebSphere Automation Module	WebSphere Deployment Manager (6, 6.1, or 7) installed on the Core Server
Windows Resource Extensions	OpenSSH for Windows 3.8.1p1-1 installed on the machine hosting the WRE Proxy Service (or an equivalent secure connection, properly configured)

2.6 Requirements for Remotely Managed Systems

As part of your planning and preparation for Application Configuration Console installation, you should also ensure that support for remotely managed systems (also known as managed servers/target systems) is in place.

Application Configuration Console requires FTP or SSH access to the remote systems that it will manage. The configured user accounts on the target systems will require read and write permissions on files and directories that contain configuration data to be imported into Integrity.

Integrity offers the following Authentication Types support for SSH:

Username and password
SSH certificates (public and private keys)
Secure provision (sudo and su to write content out to the file system)

Oracle recommends use of SSH certificates which requires that you create a dedicated user account for the application on the Application Configuration Console Server and all target systems.

Also note the following SSH/SFTP requirements for target systems:

If using SSH certificates, you must use OpenSSH to generate certificates.
SSH support requires that the SFTP subsystem be enabled on the targeted systems. The SSH configuration file (/etc/ssh/sshd_config) should contain a line similar to the following:
```
subsystem sftp /usr/lib/ssh/sftp-server
```