Table 4. Database Hardware Requirements for Deployment Server
Database Name | Minimum Requirements | IBM Recommendations |
|
|
|
SQL Server 7.0 Client (1) | Not Available | 130 MB with DBA |
|
| Note: |
|
| ODBC Administrator: 3.510.3513.0 |
|
| and later |
|
| SQL Server driver: 3.70.06.23 and |
|
| later |
|
| Access32 driver: 4.00.3513.00 and |
|
| later |
|
| Use of the incorrect version may |
|
| cause data corruption. All of these |
|
| versions are available on the Mdac |
|
| 2.1 stack. It must be obtained from |
|
| Microsoft. |
|
|
|
Oracle 8.0.5 or later Client CD(1) | Not Available | 150 MB with DBA |
|
| Required: Oracle SQL Plus 8.0.5 or |
|
| later |
|
| Note: The CD must match your |
|
| specific release. |
|
|
|
Note: |
|
|
(1) Choose one version of Oracle or SQL Server for the main database. |
| |
All other software is required. |
|
|
|
|
|
The OneWorld installation program provides you with several environments that represent the typical customer configuration. On the deployment server, these environments are preset in the installation process to provide you with an easy solution for installation setup.
In the installation process, the OneWorld installation program includes the planner environment to define the main components of a OneWorld configuration, and the deployment environment that administers system data source information, such as profiles, packages, and environments. The deployment environment uses the planner path code from the planner environment to run the OneWorld on the deployment server.
In Table 5 on page 54, the required diskspace for the objects and path codes included in the planner and deployment environments are listed.
Sizing, Considerations, and Recommendations | 53 |