Java Installation
|
 |
 |
|
|
 |
 |
The following sections provide the information you need to install and uninstall the Java Security Service Module:
Note: For installation information on other security service modules, see the associated installation guides.
Before you begin this installation procedure, make sure you have done the following:
Note: If you start the installation process from the command line or from a script, you can specify the -log option to generate a verbose installation log. For instructions on how to generate a verbose log file during installation, see Generating a Verbose Installation Log.
If you start the installation process from the command line or from a script, you can specify the -log option to generate a verbose installation log. The installation log lists messages about events during the installation process, including informational, warning, error, and fatal messages. This can be especially useful for silent installations.
Note: You may see some warning messages during in the installation log. However, unless there is a fatal error, the installation program will complete the installation successfully. The installation user interface will indicate the success or failure of the installation, and the installation log file will include an entry indicating that the installation was successful.
To create a verbose log file during installation, include the -log=/full_path_to_log_file option in the command line or script. For example:
wles422ssm_win32.exe -log=D:\logs\wles_install.log
wles422ssm_solaris32.bin -log=/opt/logs/wles_install.log
wles422ssm_linux32.bin -log=/opt/logs/wles_install.log
The path must be the full path to a file name. If the file does not exist, all folders in the path must exist before you execute the command or the installation program will not create the log file.
The procedure for starting the installation program varies depending the platform on which install BEA WebLogic Enterprise Security. Therefore, separate instructions are provide for each supported platform.
Note: In a production environment, BEA recommends that you install the Security Service Modules on machines other than the machine on which the Administration Server is installed.
To start the installation program, refer to the appropriate section listed below:
Note: Do not install the software from a network drive. Download the software distribution to a local drive on your machine and install it from there. Also, on a Windows platform, the file system used must be NTFS, not FAT. To check the file system format, open Windows Explorer and right-click the hard drive on which you intend to do the installation and select Properties.
To install the application in a Microsoft Windows environment:
wles422ssm_win32.exe.The BEA Installer - Security Service Module for Java window appears (see Figure 3-1).
If the installation program does not start automatically, open Windows Explorer and double-click the CD-ROM icon.
The BEA Installer - Security Service Module for Java window appears (see Figure 3-1).
Figure 3-1 WebLogic Enterprise Security Java Security Service Module Installer
To run graphical-mode installation, your console must support a Java-based GUI. If the installation program determines that your system cannot support a Java-based GUI, the installation program automatically starts in console-mode.
To install the application in a Sun Solaris environment:
chmod u+x wles422ssm_solaris32.bin
The BEA Installer - Security Service Module for Java window appears (see Figure 3-1).
The BEA Installer - Security Service Module for Java window appears (see Figure 3-1).
To run graphical-mode installation, your console must support a Java-based GUI. If the installation program determines that your system cannot support a Java-based GUI, the installation program automatically starts in console-mode.
To install the application in a Linux environment:
chmod u+x wles422ssm_linux32.bin
The BEA Installer - Security Service Module for Java window appears (see Figure 3-1).
The BEA Installer - Security Service Module for Java window appears (see Figure 3-1).
The installation program prompts you to enter specific information about your system and configuration, as described in Table 3-1. To complete this procedure you need the following information:
Note: If this is the first WebLogic Enterprise Security product you have installed on this machine, the Service Control Manager is also installed (which requires additional inputs such as the Service Control Manager directory).
|
Click Next to proceed or cancel the installation at any time by clicking Exit. |
|
|
Read the BEA Software License Agreement, and then select Yes to indicate your acceptance of the terms of the agreement. To continue with the installation, you must accept the terms of the license agreement, click Yes, and then click Next. |
|
|
Specify the BEA Home directory that serves as the central support directory for all BEA products installed on the target system. If you already have a BEA Home directory on your system, you can select that directory (recommended) or create a new BEA Home directory. If you choose to create a new directory, the installer program automatically creates the directory for you. For details about the BEA Home directory, see BEA Home Directory. |
|
|
Specify the directory in which you want to install the product software, and then click Next. You can accept the default product directory ( Note: You only need to install the JAVA Security Service Module once per machine. Many Java instances can be created using the same Java Security Service Module install. Refer to the Java Instance Wizard information on how to create a Java Security Service Module instance. For additional information and a description of the resulting directory structure, see Product Installation Directory. If you choose to create a new directory, the installation program automatically creates the directory for you. |
|
|
Specify the directory in which to install the Service Control Manager. You can accept the default directory ( Note: This step is required only if you are installing on a machine that does not already have an Security Control Manager installed. |
|
|
Specify the user names and group names to use for the Service Control Manager and Administration Application. You can accept the default settings or create a new ones. Note: When installing this product for use in a production environment, BEA recommends that you set these passwords to known values; otherwise you will not be able to modify them later. For example, you may want to modify these passwords to comply with organizational requirements. Admin User (asiadmin)—A local user account used to start the Administration Application components. Admin Group ( SCM User ( Security Group ( |
|
|
If the name of the user and group do not exist, they are created for you. Verify the values you entered are correct, and then click Next to continue. |
|
|
Specify the password for the Administration Application User and Service Control Manager User. You can also choose the default passwords that are randomly generated. Note: If any of the users exist you must enter their passwords; the passwords are not generated randomly. Passwords are case sensitive. If you are installing the Administration Application in a production environment, BEA recommends using secure user names and passwords, and not the user names that are randomly generated. |
|
|
Select the network interfaces to which to bind the Service Control Manager. This is the IP Address used to listen for requests to provision policy and configuration data. Note: If you are installing the product in a production environment with more than one network card, you want to select a protected (internal) interface; you do not want to expose the Service Control Manager through a public address. |
|
|
Configure Enterprise Domain for Service Control Manager (This step is required only if you are installing on a machine that does not already have an Security Control Manager installed.) |
Enterprise Domain Name—The enterprise domain name is used to link all of the WebLogic Enterprise Security components. Note: This is same enterprise domain name that you entered when you installed the BEA WebLogic Enterprise Security Administration Application. SCM Logical Name—The name you assign to the Service Control Manager during this installation. SCM Port—Port used by the Service Control Manager to receive configuration and policy data from the Administration Application; this port may not be used by any other server. Primary Server URL—The address used by your Administration Application. Backup Server URL—If you have a second Administration Application installed for the purpose of failover or backup, enter its address here. This is optional and may be left blank. |
|
Indicates that the installation completed successfully. Click Done to finish the installation. |
Now that you have installed the necessary software, you must enroll and configure the Service Control Manager, create an instance of the Security Service Module and enroll the instance, and start the services. For additional instructions, see Post Installation Tasks.
|
|
|
