N1 Grid Service Provisioning System 5.0 Installation Guide

Reference Data for the N1 Grid Service Provisioning System 5.0 on Windows

This section contains details about the installation of the N1 Grid Service Provisioning System 5.0 on Windows in the following sections:

Directory Structure of the N1 Grid Service Provisioning System 5.0 on Windows

When installing the N1 Grid Service Provisioning System 5.0, you are prompted to select a home directory for the software. The default directory is one of the following.

C:\Program Files\N1 Grid Service Provisioning System\5.0 is the directory created for the Master Server and CLI Client that contains the software.
C:\Program Files\N1 Grid Service Provisioning System is the directory created for the Local Distributor and Remote Agent that contains the software.

The installation scripts install the N1 Grid Service Provisioning System 5.0 software into default destination directories that are subdirectories of the home directory for the software. The following table lists the directories that are installed for every N1 Grid Service Provisioning System 5.0 application, the Master Server, Local Distributor, Remote Agent, and CLI Client.

Table A–6 Directories Common to All Applications


Directory	Contents
`\common`	Common files for all applications
`\common\jre`	Bundled copy of the JRE for Windows
`\common\lib`	Library files common for some or all applications

The following table lists the directories installed for the Master Server.

Table A–7 Directories Installed for the Master Server


Directory	Contents
`\server\config`	Master Server Configuration files
`\server\data`	Master Server data files
`\server\bin`	Master Server Executable files
`\server\lib`	Master Server-specific library files
`\server\postgres`	Bundled copy of Postgres
`\server\cygwin`	Bundled subset of Red Hat cygwin
`\server\tomcat`	Bundled copy of Apache Tomcat
`\server\webapp`	Browser Interface Web Application
`\server\setup`	Miscellaneous files used to initialize the Master Server
`\server\data\tmp`	Master Server temporary directory with permissions set to 777
`\server\README`	Text license agreement

The following table lists the directories installed for the Local Distributor.

Table A–8 Directories Installed for the Local Distributor


Directory	Contents
`\ld\config`	Local Distributor configuration files
`\ld\bin`	Local Distributor executable files
`\ld\lib`	Local Distributor library files
`\ld\data`	Local Distributor-specific data
`\ld\data\tmp`	Local Distributor temporary directory
`\ld\jvm\jre\bin`	Local Distributor JRE proxy
`\ld\README`	Text license agreement

The following table lists the directories installed for the Remote Agent.

Table A–9 Directories Installed for the Remote Agent


Directory	Contents
`\agent\config`	Remote Agent configuration files
`\agent\bin`	Remote Agent executable files
`\agent\lib`	Remote Agent library files
`\agent\data`	Remote Agent-specific data
`\agent\work`	Default directory for execution of execNatives
`\agent\data\tmp`	Remote Agent temporary directory
`\agent\jvm\jre\bin`	Remote Agent JRE proxy
`\agent\README`	Text license agreement

The following table lists the directories installed for the CLI Client.

Table A–10 Directories Installed for the CLI Client


Directory	Contents
`\cli\config`	CLI configuration files
`\cli\bin`	CLI executable files
`\cli\lib`	CLI library files
`\cli\data`	CLI specific data
`\cli\data\tmp`	CLI temporary directory with permissions set to 777
`\cli\README`	Text license agreement

Cygwin

To facilitate interoperability with applications running on Solaris OS, Red Hat Linux, and IBM AIX servers, the Windows version of the software includes a subset of the Red Hat cygwin UNIX environment. The following description of cygwin comes from the official Cygwin web site at http://www.cygwin.com.

Cygwin is a UNIX environment, developed by Red Hat, for Windows. It consists of two parts: - A DLL (cygwin1.dll) which acts as a UNIX emulation layer providing substantial UNIX API functionality. - A collection of tools, ported from UNIX, which provide UNIX/Linux look and feel. The Cygwin DLL works with all non-beta, non “release candidate”, ix86 versions of Windows since Windows 95, with the exception of Windows CE.

Actions Performed by the Windows Installation Scripts

The Windows Master Server installation script performs the following actions:

Copies all installation contents to the directories you specified.
Sets up the registry entries for the proper mount points for cygwin.
Registers the cygipc service.
Registers the postmaster service with a dependency on the cygipc service.
Registers the Master Server service with a dependency on the postmaster service.
Creates a Start menu shortcut.
If you selected SSL as a communications protocol, runs scripts to generate the configuration files that are needed for SSL.

The Windows Local Distributor installation script performs the following actions:

Copies the installation contents to the directories you specified.
If you selected SSL as a communications protocol, runs scripts to generate the configuration files that are needed for SSL.
Registers the Local Distributor service.
Creates a Start menu shortcut.
If you requested that the installation script start the Local Distributor, starts the Local Distributor.

The Windows Remote Agent installation script performs the following actions:

Copies the installation contents to the directories you specified.
If you selected SSL as a communications protocol, it runs scripts to generate the configuration files that are needed for SSL.
Registers the Remote Agent service.
Creates a Start menu shortcut.

The Windows CLI Client installation script performs the following actions:

Copies the installation contents to the directories you specified.
If you selected SSL as a communications protocol, runs scripts to generate the configuration files that are needed for SSL.
Creates a Start menu shortcut.