1 — Installing NetCrusader/CORBA

[Previous] [Next] [Table of Contents]

This chapter contains the following sections:

1.1 Installation Prerequisites
1.2 Overview of NetCrusader/CORBA Components
1.3 Installing NetCrusader/CORBA Components
1.4 Java Installation Notes

NOTE: The NetCrusader/CORBA Release Notes includes the latest information regarding installation procedures, supported platforms, and known problems for the Beta Release of NetCrusader/CORBA. Where information in this guide differs from that in the release notes, use the information in the release notes.

1.1 Installation Prerequisites

This section describes prerequisites to installing NetCrusader/CORBA.

Supported Platforms

Security Server. You can install the NetCrusader/CORBA Security Server only on systems running Windows NT 4.0 Server with Service Pack 3.0 or later.

CORBA Server. You can install the CORBA server components of NetCrusader/CORBA only on systems running Windows NT 4.0 Workstation or Server with Service Pack 3.0 or later.

CORBA Client. You can install CORBA client components on systems running Windows NT 4.0 with Service Pack 3.0 or later.

NetCrusader Commander. You can install NetCrusader Commander only on systems running Windows NT 4.0 Workstation or Server with Service Pack 3.0 or later.

NetCrusader Commander is implemented as a Microsoft Management Console (MMC) snap-in. Microsoft Management Console (MMC) 1.1 must be installed on the system on which you plan to install NetCrusader Commander.

MMC requires Internet Explorer 4.01 or later. For this reason, Internet Explorer 4.01 must be installed on the system on which you intend to run NetCrusader Commander.

For more information about NetCrusader/CORBA components, see Section 1.2.

VisiBroker Support

Before you install NetCrusader/CORBA, the following version of Inprise VisiBroker™ must be installed on all systems that will run secure CORBA servers:

• VisiBroker for Java Version 3.3 or 3.4 for Windows NT
  

Figure 1-1 shows a sample configuration, in which a CORBA application server system doubles as the Master Security Server and can also be used to manage the security environment using NetCrusader Commander.

A second system is installed with the NetCrusader/CORBA Security Server so that it can be used as a Security Server replica.

CORBA application clients are running the NetCrusader/CORBA client components.

Figure 1-1: Sample Configuration

1.1.2 Order of Installation

You should first install and configure the system that will house the Master Security Server.

Then, install and configure any Replica Security Servers. Once these are installed, install NetCrusader/CORBA on any CORBA server and CORBA client systems, and install NetCrusader Commander on systems that you plan to use for management.

1.2 Overview of NetCrusader/CORBA Components

NetCrusader/CORBA provides a one-button installation program that installs all of the components a system requires. You can easily configure clients by entering the hostname of your Security Server during the installation process.

NetCrusader/CORBA includes the following components:

• NetCrusader/CORBA Security Server
  
• CORBA Application Server and Client Components
  
• NetCrusader Commander
  

The NetCrusader/CORBA Security Server provides the ORB security functionality for application servers, and provides a centralized security registry, which contains user names and passwords, groups and organization membership lists, and other customizable registry attributes.

You are required to have at least one NetCrusader/CORBA Security Server running in your secure environment. If you intend to replicate the Security services, install at least two NetCrusader/CORBA Security Servers.

CORBA Server and Client Components

The NetCrusader/CORBA Java CORBA Security Runtimes for CORBA application servers and clients provides the functionality that interacts with the ORB for security.

The Java CORBA Security Runtime is responsible for securing the IIOP traffic between clients and servers and enforcing the security policies you define. This runtime also implements the CORBA Security application programming interfaces (APIs). The Java security runtime is implemented as a set of Java classes that integrates into the ORB.

NetCrusader Commander

Install NetCrusader Commander on Windows NT systems that you plan to use for domain administration. NetCrusader Commander is a graphical administration program implemented as a Microsoft Management Console (MMC) snap-in. Microsoft Management Console Version 1.1 is included in the NetCrusader/CORBA installation.

1.3 Installing NetCrusader/CORBA Components

The NetCrusader/CORBA installation includes the Security Server, Client, and, optionally, NetCrusader Commander, the graphical management program you use for user, group, domain, policy, and required rights administration.

Starting the Installation Process

Begin the installation process by inserting the NetCrusader/CORBA CD into your CD-ROM drive and running setup.exe.

1. Follow the installation prompts to accept the software license agreement, and enter user information.

2. When you reach the Choose Software screen, select the components you want to install.

NOTE: CORBA Server systems must be running Windows NT 4.0 Workstation or Server with Service Pack 3 or later.

Installing the Security Server

If you selected Security Server at the Choose Software screen, the Security Server Type screen appears.

1. Select:
   • Master — If this system will house the main Security Server.
     
   • Replica — If this system will house a backup Security Server.
     

2. If you chose Master, the Security Server Identification screen appears. Enter the administrator's username and password.

   The username and password you use when you install the Master Security Server sets the username and password that will be requested during subsequent NetCrusader/CORBA installations.

3. If you chose Replica, the Master Host Name screen appears. Enter the DNS name of the system that houses the Master Security Server. Use the following format: systemname.domain.com.

   Click Next. The Security Server Identification screen appears. Enter the administrator's username and password for the Master Security Server.

4. Click Next. The Choose Destination Location screen appears. Accept the default location for this component or browse to a new location.

5. Click Next. The installation program installs the Security Server.

   Installing the CORBA Server

CORBA Server systems must be running Windows NT 4.0 Workstation or Server with Service Pack 3 or later. You have the option of using a CORBA Server system as a NetCrusader/CORBA Master or Replica Security Server. Refer to Section 1.3 for instructions.

If you selected CORBA Object Server at the Choose Software screen, the Choose Destination Location screen appears.

1. Accept the default location or browse to a new location and click Next.

   Click Next. The Security Server Identification screen appears.

2. Select either:
   • Modify the Registry — Modifies your system path.

   • Do not modify the Registry — Does not modify your system path.

     Click Next. The Current Settings screen appears, allowing you to review your choices.

     Click Next when you are satisfied with your choices. The installation program installs the CORBA Server.

     Installing the CORBA Client Server

If you selected CORBA Client Server at the Choose Software screen, the components are installed, but you are not asked to specify where to install the software. After you install the software, you do not see CORBA Client in the NetCrusader/CORBA program group.

1.3.1 After Installation

After you have installed the required NetCrusader/CORBA components on all systems in your environment, refer to Chapter 2 for configuration instructions.

If you are running NetCrusader/CORBA in a Java environment, see Section 1.4 for important installation notes.

1.4 Java Installation Notes

The information in this section applies only to NetCrusader/CORBA in the Java environment.

The NetCrusader/CORBA installation program sets the System CLASSPATH variable to include the Gradient .JAR files. If a system on which you install NetCrusader/CORBA has a User CLASSPATH variable set, the User variable overrides the System variable, and NetCrusader/CORBA will not operate correctly.

• If the system has a User CLASSPATH variable set, edit the User variable to include the following files:

  <install directory>\Gradient\NetCCorba\Lib\NetCCorba.jar

  You can copy and paste this information from the System CLASSPATH variable.

  The file NetCCorba.jar must precede the file vbjorb.jar (the VisiBroker ORB jar file) in the class path.

• If the system has no User CLASSPATH variable set, there is no need for any alterations. Do not add a User CLASSPATH variable.

To determine if the system has a User CLASSPATH variable set, check the Environment tab on the System Properties page, which is accessible from the Control Panel.

[Previous] [Next] [Table of Contents]

To make comments or ask for help, contact support@gradient.com.

Copyright © 1999 Gradient Technologies, Inc.