Overview of the N1 Service Provisioning System 4.1 Installation Tasks
The task map below describes the tasks necessary to properly install and configure the N1 Service Provisioning System 4.1.
Table 1–1 Task Map: Installing the N1 Service Provisioning System 4.1|
Task |
Description |
For Instructions |
|---|---|---|
|
Review system requirements. |
Determine whether your system meets the minimum requirements to install. |
Chapter 2, System Requirements for the N1 Service Provisioning System 4.1 |
|
Gather information for installation. |
Before installing, gather the information that you will need to install the product. | |
|
(Optional) Create a user account. |
You can create a special, operating system user account to be used by N1 Service Provisioning System 4.1. |
The documentation for your operating system. |
|
(Optional) Install Jython on CLI Client machines. |
You may choose to install Jython on any machine from which you want to run the CLI Client. Jython is not required to run the CLI Client. Jython is available from . |
The Jython web site. |
|
Install the applications. |
You will install each of the N1 Service Provisioning System 4.1 applications individually using the appropriate installation script provided on the product media. |
Chapter 5, Installing the N1 Service Provisioning System 4.1 on Windows Systems |
|
(Optional) Configure SSH. |
If you plan to access the Master Server on the Internet, you can increase the Master Server security by configuring the N1 Service Provisioning System 4.1 to use SSH to communicate with that server. |
Chapter 6, Configuring the N1 Service Provisioning System 4.1 to Use Secure Shell |
|
(Optional) Configure SSL. |
If you want to provide the maximum security for communication among the applications, configure the applications to use SSL when communicating. SSL support is based on self-signed digital certificates that your organization can issue to itself. |
Chapter 7, Configuring the N1 Service Provisioning System 4.1 for SSL |
|
(Optional) Configure the JVM Security Policy. |
If you do not use SSL to provide security for communication among application, you can configure the JVM security policy so that the applications accept only connections from localhost. This setup provides a minimum level of security. |
Chapter 8, Configuring the Java Virtual Machine Security Policy |
- © 2010, Oracle Corporation and/or its affiliates