Install WebSphere
Follow the WebSphere installation instructions as described in the IBM documentation.
When installing WebSphere, consider that WebSphere 6.x uses default messaging (embedded messaging for WebSphere 5.1), which is installed with the WebSphere server.
Verify WebSphere is Working
Use the snoop utility provided by IBM to verify that WebSphere is installed correctly before installing the Administrative UI.
To verify WebSphere is working
Example: http:MyServer.MyCompany.com:9080/snoop.
If WebSphere is installed correctly, Snoop Servlet—Request Client Information page is displayed in the browser.
Example: http://MyServer.MyCompany.com/snoop
If WebSphere is installed correctly, the same Snoop Servlet—Request Client Information page is displayed in the browser.
You have verified that WebSphere is working properly.
Note: Contact IBM Technical Support for additional assistance with WebSphere.
A trusted relationship between the Administrative UI and a Policy Server is required to begin managing your environment. You establish this relationship the first–time you log in using the default SiteMinder super user account (siteminder) and password. These credentials are stored in the policy store.
When you configure the policy store, you use the XPSRegClient utility to submit the super user credentials to the Policy Server. The Policy Server uses these credentials to verify that the registration request is valid and that the relationship can be created.
Note: If you used the Policy Server installer to configure the policy store automatically, the installer used the XPSRegClient utility to submit the credentials.
The time from which the credentials are supplied to when the initial Administrative UI login can occur is limited to 24 hours. Therefore, the process for installing the Administrative UI is determined by when the policy store is configured and the Administrative UI is installed.
Complete the following before you install the Administrative UI:
If the policy store was configured more than 24 hours ago, use the XPSRegClient utility to submit the default SiteMinder super user account credentials to the Policy Server before installing the Administrative UI. The Policy Server requires these credentials to create a trusted relationship with the Administrative UI.
Note: For a list of supported CA and third-party components, refer to the SiteMinder r12.0 SP3 Platform Support Matrix on the Technical Support site.
Complete the following procedures to install the Administrative UI:
Certain library files are required for components operating on Linux operating environments. Failure to install the correct libraries can cause the following error:
java.lang.UnsatisfiedLinkError
If you are installing, configuring, or upgrading a Linux version of this component, the following libraries are required on the host system:
compat–gcc-34-c++-3.4.6-patch_version.I386
libstdc++-4.4.6-3.el6.i686.rpm
To have the appropriate 32-bit C run–time library for your operating environment, install the previous rpm.
libXau-1.0.5-1.el6.i686.rpm
libxcb-1.5-1.el6.i686.rpm
libstdc++-4.4.6-4.el6.i686.rpm
compat-db42-4.2.52-15.el6.i686.rpm
compat-db43-4.3.29-15.el6.i686.rpm
libX11-1.3-2.el6.i686.rpm
libXrender-0.9.5-1.el6.i686.rpm
libexpat.so.1 (provided by expat-2.0.1-11.el6_2.i686.rpm)
libfreetype.so.6 (provided by freetype-2.3.11-6.el6_2.9.i686.rpm)
libfontconfig.so.1 (provided by fontconfig-2.8.0-3.el6.i686.rpm)
libICE-1.0.6-1.el6.i686.rpm
libuuid-2.17.2-12.7.el6.i686.rpm
libSM-1.1.0-7.1.el6.i686.rpm
libXext-1.1-3.el6.i686.rpm
compat-libstdc++-33-3.2.3-69.el6.i686.rpm
compat-db-4.6.21-15.el6.i686.rpm
libXi-1.3-3.el6.i686.rpm
libXtst-1.0.99.2-3.el6.i686.rpm
libXft-2.1.13-4.1.el6.i686.rpm
libXt-1.0.7-1.el6.i686.rpm
libXp-1.0.0-15.1.el6.i686.rpm
The Administrative UI installer requires specific information about the application server that is installed on the Administrative UI host system.
The following sections detail the required information depending on the type of application server.
Note: Worksheets are provided to help you gather and record required information before installing the Administrative UI.
Gather the following information about JBoss before installing and registering the Administrative UI:
The path to the folder where JBoss is installed.
The fully qualified URL of the JBoss host system.
The installation location of the required JDK.
Gather the following information before installing and registering the Administrative UI:
The path to the WebLogic installation directory.
The path to the WebLogic domain you created for the Administrative UI.
The name of the WebLogic server on which the WebLogic domain is configured.
The fully qualified URL of the WebLogic host system.
The installation location of the required JDK.
Gather the following information about WebSphere before installing and registering the Administrative UI:
The full path to the folder in which WebSphere is installed.
The fully qualified URL of the WebSphere host system.
The name of the application server.
The name of the profile being used for the Administrative UI.
The name of the cell where the server is located.
The name of the node where the server is located.
The installation location of the required JDK.
The following sections detail how to install the Administrative UI to an existing application server infrastructure.
|
Copyright © 2012 CA.
All rights reserved.
|
|