A Installation Checklists and Worksheet
We strongly recommend that you use the following installation checklists when installing both Oracle Database software and Oracle Communications IP Service Activator components.
These checklists are designed to:
-
Provide a quick reference to the recommended installation settings for each installation task
-
Enable you to record any user-specific settings you may decide to enter during an installation task
-
Help you to provide important configuration information to Oracle GCS when troubleshooting installation problems
Checklists include:
Oracle Database Installation Data
Table A-1 is designed to help determine the size of a new network.
Table A-1 Oracle Database Installation Data Worksheet
| Setting | Attribute | Recommended | Recorded value |
|---|---|---|---|
|
Oracle Database home settings |
Location |
/usr/local/oracle/u01/app/oracle/product/version |
|
|
NetCA service connection settings |
Global Database Name |
IPSA.WORLD |
|
|
Not applicable |
Net Service Name |
IPSA |
* |
|
Not applicable |
Host Name (IP Service Activator database) |
None supplied |
|
|
Not applicable |
Database SID |
IPSA |
* |
|
IP Service Activator database settings |
Tablespace name |
IPServiceActivatorDb |
|
|
Not applicable |
Datafile Name |
/usr/local/oracle/u01/app/oracle/oradata/IPSA/IPSERVICEACTIVATORDB.dbf |
|
|
Not applicable |
File Size |
250 MB |
|
|
Not applicable |
Increment |
5 MB |
|
|
Oracle Database Listener settings |
Global name |
IPSA.WORLD |
|
|
IP Service Activator database login settings |
Database userID |
admin |
* |
|
Not applicable |
Password |
admin |
* |
*These items are entered when installing the IP Service Activator Policy Server, client, and they must be identical to those defined here.
IP Service Activator Multi-host General Installation Checklist
Complete one copy of Table A-2 for each host.
Table A-2 Multi-Host General Installation Checklist
| Setting | Attribute | Recommended | Recorded value |
|---|---|---|---|
|
Server hostname |
|
|
|
|
Serial Number |
|
If you were provided with a serial number by Oracle Communications for a previous deployment, you must re-enter that value for the new deployment. |
|
|
Installed Files Location |
Destination Folder |
Use default supplied |
|
|
Naming service settings |
Hostname |
None supplied Record local hostname for reference when installing other components. |
|
|
Not applicable |
TCP/IP Port |
2809 |
|
|
Database connection settings |
Data Source Name (DSN) |
IPServiceActivatorDb Check Oracle Database installation |
|
|
Not applicable |
Database Server IP Address |
None supplied |
|
|
Not applicable |
Database Server Port |
Use default 1521 |
|
|
Not applicable |
Database Service Name (SID.DOMAIN) |
IPSA.WORLD Check Oracle Database installation |
|
|
Not applicable |
Database Userid |
admin Check Oracle Database installation |
|
|
Not applicable |
Database User Password |
admin Check Oracle Database installation |
|
|
IP Service Activator Program Folder |
Program Folders |
Use default supplied |
|
Client Installation Checklist
The task in Table A-3 is described in the additional setup tasks to be run prior to initial startup topic in IP Service Activator System Administrator's Guide.
Table A-3 Client Installation Checklist
| Setting | Attribute | Recommended | Recorded value |
|---|---|---|---|
|
Install Files Location |
Destination Folder |
Use default supplied |
|
|
Naming service settings |
Hostname |
Use Policy Server hostname |
|
|
Not applicable |
TCP/IP Port |
2809 |
|
|
IP Service Activator Program Folder |
Program Folders |
Use default supplied |
|
Site Survey Worksheet
Table A-4 can help to determine the size of a new network. Use the survey data to determine the appropriate hardware for an IP Service Activator deployment. Being able to answer the questions in this list prior to contacting Oracle Global Customer Support for assistance, can also speed the resolution of sizing and support issues.
Table A-4 Site Survey Worksheet
| Deployment Characteristics | Recorded Values |
|---|---|
|
Devices: |
|
|
Number of managed PEs and vendor type(s) |
|
|
Average number of interfaces/sub-interfaces/VC-endpoints per PE device |
|
|
If Configuration Management module is deployed, average number of device configuration archives per PE to be retained |
|
|
Number of managed CEs and vendor type(s) |
|
|
Average number of interfaces/sub-interfaces/VC-endpoints per CE device |
|
|
If Configuration Management module is deployed, average number of device configuration archives per CE to be retained |
|
|
VPNs: |
|
|
Number of user VPN connections (Sites) |
|
|
QoS: |
|
|
Number of concrete policy elements |
|
|
Breakdown on a per policy element basis if possible |
|
|
Miscellaneous IP Service Activator activity: |
|
|
Number of GUI logins per day |
|
|
Number of device discoveries and capability fetches per day (the size and nature of CEs and PEs that are likely to be discovered affect discovery times) |
|
|
PEs (average number of interfaces per device) |
|
|
CEs (average number of interfaces per device) |
|
|
System component usage: |
|
|
OSS Integration Manager (OIM) (deployment generates additional CPU demand on the Policy Server host machine) |
|
|
Maximum number of concurrent GUI users |
|
|
System configuration: |
|
|
Is Citrix usage in use? |
|
|
List of all other implementation-specific restrictions: |
|
|
Bandwidth limitations (if any) |
|
|
Cost considerations |
|
|
Other deployment issues |
|