Installing the Oblix Netpoint InfrastructurePage 1 of 31
Farmers Insurance
Installing the Oblix Netpoint 6.1 Infrastructure
Table of Contents
Table of Contents
1.Introduction
1.1.Summary
1.2.Components Checklist
2.Preparing the LDAP Instance
3.Installing Oblix Netpoint CoreID
1.3.Installing the latest Java Development kit. JDK 1.4.
1.3.1.Obtaining the installation file.
1.3.2.Running the installation command.
1.3.3.Modify the variable CLASSPATH.
1.4.Installing the CoreID binaries
Obtain the installation file.
Run the installation command.
4.Creating the Web Server Instance
5.Installing Oblix Netpoint WebPass
6.COREiD System Setup
7.Adding Custom Farmers Look and Feel
1.5.Backing up the Basic Oblix Netpoint Installation.
1.6.Copying the Custom Look and Feel Files
1.7.Moving GIFs and JS files.
8.Adding Farmers Custom Coding
- Introduction
1.1.Summary
This purpose of this document is to provide details for the migration of Oblix Infrastructure from the Development environment to the QA environment.
We assume that a QA environment is installed.
Migrating the Oblix Netpoint 6.1 infrastructure from Development to QA consists of the following major steps.
- Preparing the LDAP Instance.
- Installing Oblix Netpoint CoreID Server.
- Installing the Webserver Instance.
- Installing Oblix Nepoint Webpass
- CoreID System Setup
- Adding Custom Farmers Look and Feel.
- Adding Custom Frmers Coding.
1.2.Components Checklist
Component / Parameter / Development / QALDAP Server Hostname / <ldap server hostname> / Hm2uxox01 / Hm2ntsm01
LDAP Server Port / <ldap server port> / 390 / 389
LDAP Server IP / <ldap server ip>
COREiD Server Hostname / <coreid server hostname> / hm2uxds02 / Hm2uxds02
COREiD Server IP / <coreid server ip>
COREiD Server Instance ID / <coreid server instance id> / Netpointqa01 / Netpoint01
COREiD Server/ WebPass Port / <coreid server/ webpass port> / 6024 / 6022
COREiD Server user name (UNIX) / <coreid server user name> / nobody / Nobody
COREiD Server group (UNIX) / <coreid server group> / nobody / Nobody
COREiD Server Installation Directory / <coreid server installation directory> / /opt/netpointqa / /opt/netpoint
Web Server Hostname / <web server hostname> / Testoblix / hm2uxeb04
hm2uxeb05
Web Server user name / <web server user name> / nobody / Nobody
Web Server group name / <web server group name> / nobody / Nobody
WebPass Instance ID / <webpass instance id> / Webpa01 / Webpass01
WebPass Installation Directory / <webpass installation directory> / D:\oblixqa\
webcomponent / /opt/netpoint/
webcomponent
Siteminder / Hm2ntsm04 and
Hm2uxsp01
Software Description / Software Locations
Netpoint 6.1 Schema Files: / Host:
Hm2ds02 /opt/softwares/netpointldifs
Oblix Object from the QA Server hm2ntsm01 / Hm2ds02 /opt/softwares/netpointldifs/sm0oblixobject.ldif
Oblix Object from Development server hm2uxox01 / Hm2ds02 /opt/softwares/netpointldifs/ux01oblixobject.ldif
CoreID Install Binaries / hm2ds02
/opt/softwares/ NetPoint6_1_EN_sparcs2_COREid_Server
Webpass Install Binaries / Testoblix D:\install\netpoint_webpass.exe
For Unix, Nagaraj has:
hm2ds02
/opt/softwares/NetPoint6_1_EN_sparcs2_NSAPI_WebPass
Farmers Custom Look and Feel for CoreID (xml and xsl files) / Hm2uxds02
/opt/softwares/customlook/copyxmlxsl
Farmers Custom Look and Feel for CoreID (gif and js files) / Testoblix
c:\gifcopy.bat
On unix:
Hm2uxds02 /opt/softwares/customgifs/admin
Hm2uxds02 /opt/softwares/customgifs/common
Hm2uxds02 /opt/softwares/customgifs/userservcenter
Hm2uxds02 /opt/softwares/customgifs/selector
Farmers Custom Coding / Hm2uxds02
/opt/softwares/custom_17Sep2003.tar
- Preparing the LDAP Instance
Import Oblix6.x schema into QA LDAP Server / On hm2uxds01:
/opt/ldap/server4/shared/bin
For 4.x servers
ldapmodify –D “cn=directory manager” –w XXXXXX –hm2ntsm01 –p 389 –a –c –f /opt/softwares/netpointldifs/iPlanet_oblix_schema_add.ldif
ldapmodify –D “cn=directory manager” –w XXXXXX –hm2ntsm01 –p 389 –a –c –f /opt/softwares/netpointldifs/ iPlanet4_oblix_index_add.ldif
For 5.x servers (Replicas)
ldapmodify –D “cn=directory manager” –w XXXXXX –hm2uxld07 –p 389 –a –c –f /opt/softwares/netpointldifs/iPlanet_oblix_schema_add.ldif
ldapmodify –D “cn=directory manager” –w XXXXXX – hm2uxld07 –p 389 –a –c –f /opt/softwares/netpointldifs/ iPlanet5_oblix_index_add.ldif
Do this for the replicas:
ldapmodify –D “cn=directory manager” –w XXXXXX –hm2uxld08 –p 389 –a –c –f /opt/ldap/netpointldifs/iPlanet_oblix_schema_add.ldif
ldapmodify –D “cn=directory manager” –w XXXXXX – hm2uxld08 –p 389 –a –c –f /opt/ldap/netpointldifs/ iPlanet5_oblix_index_add.ldif
Notes: Check on these entries on ds01 – 395
adding new entry cn=obaccessuid,cn=index,cn=config,cn=ldbm
ldap_add: Already exists
adding new entry cn=obattr,cn=index,cn=config,cn=ldbm
ldap_add: Already exists
adding new entry cn=obid,cn=index,cn=config,cn=ldbm
ldap_add: Already exists
adding new entry cn=obindirectmanager,cn=index,cn=config,cn=ldbm
ldap_add: Already exists
adding new entry cn=oblocationdn,cn=index,cn=config,cn=ldbm
ldap_add: Already exists
adding new entry cn=obmodifyaccessuid,cn=index,cn=config,cn=ldbm
ldap_add: Already exists
adding new entry cn=obnotifyuid,cn=index,cn=config,cn=ldbm
ldap_add: Already exists
adding new entry cn=obparentlocationdn,cn=index,cn=config,cn=ldbm
ldap_add: Already exists
Stop the LDAP server instance / ./stop*Modify the slap.conf
Pound out the include statements for:
slapd.at.oblix.conf
slapd.oc.oblix.conf / Stop QA server instance
/opt/ldap/server4/slapd-hm2uxds01/stop*
vi /opt/ldap/server4/slapd-hm2uxds01/config/slapd.conf
Start the LDAP server instance / ./stop*
Export the hm2ntsm01 o=oblix,o=farmers.com / ./ldapsearch -D "cn=directory manager" -w XXXX -h hm2ntsm01 -p 389 -s sub -b o=oblix,o=farmers.com -T > /opt/softwares/netpointldifs/sm01oblixobject.ldif
Delete the o=oblix,o=farmers.com container in hm2ntsm01, port 389
Migration of o=oblix,o=farmers.com Container from Dev to QA filename: ox01oblixobject.ldif / ./ldapmodify –D “cn=directory manager” –h hm2ntsm01 –p 389 –a –c –f /opt/softwares/netpointfiles/ox01oblixobject.ldif
Reimport the container o=oblix,o=farmers.com back into QA. Filename: sm01oblixobject.ldif / ./ldapmodify –D “cn=directory manager” –h hm2ntsm01 –p 389 –a –c –f /opt/softwares/netpointfiles/ox01oblixobject.ldif
Modify the LDAP Instance entries. / The following describes this process.
We have to delete some entries from LDAP, which is related to style sheets. This is
because we have 3.6 style sheet related info present in this LDAP.If you don’t delete
these entries then new Oblix will try to look for this stylesheet dir that is present in LDAP
and will not work.
Delete certain oblix attributes. / The entries we need to delete aredelete obdefaultonlystyle and obdefaultstyle for the entry o=oblix,o=farmers.com
Alternatively, Through the admin console delete obdefaultonlystyle and obdefaultstyle.
In the container
ou=WebResrcDB, ou=policies, o=oblix, o=farmers.com
delete entries related to CoreId server details, WebPass details and another entry with timestamp .
These entries are related to a former environment from which Oblix data was taken and is not appropriate for the new environment. So these entries need to be deleted.
Delete every entry until the following are remaining:
Common, corpdir, objservcenter, userservcenter,groupservcenter, and MasterAuditPolicy
Make all attributes for the farmerstable objectclass optional. / This procedure is well documented else and will be included in this documentation at a later date.This has to be done on the Master and all the Replicas.
Restart LDAP instance. / This procedure is well documented else and will be included in this documentation at a later date.
Installing Oblix Netpoint CoreID
1.3.Installing the latest Java Development kit. JDK 1.4.
Skip this step for the QA Migration.
1.3.1.Obtaining the installation file.
The installation file is located on hm2uxds02 in /opt/softwares.
1.3.2.Running the installation command.
1.3.3.Modify the variable CLASSPATH.
set CLASSPATH=$CLASSPATH:/opt/j2sdk1.4.1_05/jre/lib/rt.jar:.:/opt/custom/lib/Xerces2.4/tools/ant.jar:/opt/custom/lib/Xerces2.4/tools/xercesImpl.jar:/opt/custom/lib/Xerces2.4/tools/optional.jar:/opt/custom/lib/Xerces2.4/tools/xalan.jar:/opt/custom/lib/Xerces2.4/tools/xml-apis.jar:/opt/custom/lib/Xerces2.4/tools/junit.jar:/opt/custom/lib/Xerces2.4/tools/stylebook-1.0-b2.jar:/opt/custom/lib/jars/netscape1.1.jar
1.4.Installing the CoreID binaries
CoreID Instance: coreidqa01
CoreID Installation path: /opt/netpoint
Hostname for CoreID: hm2uxds02
Port: 6022
For each of the following steps, follow the instructions in the left column. Parameter values for each installation may not necessarily match exactly the information in the screenshots on the right.
This section covers the installation of COREiD for a demonstration server and uses non-production parameters. If this section is to be used for Production installation, use Production values instead.
Obtain the installation file.
The installation file is located on hm2uxds02 in /opt/softwares.
Run the installation command.
Log on as root on the UNIX machine <coredid server hostname>(hm2uxlds02)
Change directory to the directory with the installation binary.
Run the installation binary.
Press Enter. / # ./NetPoint6_1_EN_sparc-s2_COREid_Server
InstallShield Wizard
Initializing InstallShield Wizard...
Preparing Java(tm) Virtual Machine...
......
......
......
......
......
......
.
Running InstallShield Wizard...
Welcome to the InstallShield Wizard for Oblix NetPoint 6.1 COREid Server
The InstallShield Wizard will install Oblix NetPoint 6.1 COREid Server on your
computer.
To continue, click Next.
Oblix NetPoint 6.1 COREid Server
Oblix, Inc.
Please press Enter to Continue
Press Enter. / Please read the following license agreement carefully.
Oblix Evaluation License Agreement
OBLIX EVALUATION LICENSE AGREEMENT (UNIX)
------
1. IMPORTANT RESTRICTIONS AND WARNINGS
1.1 Evaluation Time Period. The license key key provided will
permit usage of the Software for only 60 days. THE SOFTWARE WILL
AUTOMATICALLY DISABLE ITSELF AFTER 60 DAYS.
1.2 Number of Users. Company may only use the Software with
up to 100 users.
1.3 Total Disclaimer of Liability. IN NO EVENT SHALL OBLIX
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL OR
CONSEQUENTIAL DAMAGES, LOSSES, COSTS OR EXPENSES OF ANY KIND,
HOWEVER CAUSED AND WHETHER BASED IN CONTRACT, TORT (INCLUDING
NEGLIGENCE), PRODUCTS LIABILITY OR ANY OTHER THEORY OF LIABILITY,
INCLUDING BUT NOT LIMITED TO LOST PROFITS, COSTS OF PROCUREMENT
OF SUBSTITUTE GOODS, LOSS OF GOODWILL, LOSS OF DATA OR SYSTEM
USE, AND OTHER BUSINESS LOSS, REGARDLESS OF WHETHER OBLIX KNOWS
OR HAS BEEN ADVISED OF SUCH DAMAGES, LOSSES, COSTS OR EXPENSES.
1.4 Disclaimer. OBLIX MAKES, AND COMPANY RECEIVES, NO
Press ENTER to read the text [Type q to quit]
Press Enter. / WARRANTIES OR CONDITIONS OF ANY KIND, WHETHER EXPRESS, IMPLIED,
STATUTORY OR OTHERWISE, RELATED TO OR ARISING OUT OF THIS
AGREEMENT. ALL SOFTWARE, MATERIALS AND INFORMATION FURNISHED
UNDER OR IN CONNECTION WITH THIS AGREEMENT ARE PROVIDED "AS IS,"
AND OBLIX SPECIFICALLY DISCLAIMS THE IMPLIED WARRANTIES OR
CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE,
SATISFACTORY QUALITY AND NON-INFRINGEMENT, AND ALL OTHER IMPLIED
WARRANTIES THAT MAY OTHERWISE ARISE FROM COURSE OF DEALING, USAGE
OF TRADE OR CUSTOM.
1.5 U.S. Government Rights. If Company is an agency,
department, or other entity of the United States government
("Government"), Company's use, reproduction, release,
modification, disclosure or transfer of the Software, or of any
related documentation of any kind, including technical data, is
restricted in accordance with Federal Acquisition Regulation
("FAR") 12.212 for civilian agencies and Defense Federal
Acquisition Regulation Supplement ("DFARS") 227.7202 for military
agencies. The Software is commercial. The use of the Software
by any Government agency, department, or other entity of the
Government, is further restricted in accordance with the terms of
Press ENTER to read the text [Type q to quit] q
Enter 1.
Press Enter. / [ ] 1 - I accept the terms of the license agreement.
[X] 2 - I do not accept the terms of the license agreement.
You cannot proceed with this option [0] 1
Press Enter. / [X] 1 - I accept the terms of the license agreement.
[ ] 2 - I do not accept the terms of the license agreement.
To select a choice enter its number, or 0 when you are finished [0]:
Press Enter. / Please press Enter to Continue
Press Enter to accept the default. / The product that you are about to install needs to be owned by a dedicated
user. Only root or the dedicated user may be able to start the service. Most of
the time the server is run as `root' or `nobody'.
Enter the username the COREid server is running as [nobody]
Press Enter to accept the default. / Enter the Group for the above username [nobody]
Type:
<netpoint install directory>
(/opt/netpointdemo)
Press Enter. / Please specify the installation directory for Oblix NetPoint 6.1 COREid Server.
Please specify a directory name or press Enter [/opt/netpoint] /opt/netpointdemo
Press Enter. / Please press Enter to Continue
Press Enter. / Oblix NetPoint 6.1 COREid Server will be installed in the following location:
/opt/netpointdemo/identity
for a total size:
248.6MB
Please make a note of the Oblix NetPoint 6.1 COREid Server installation
directory: /opt/netpointdemo/identity because you will need to refer to it in
the future.
Please press Enter to Continue
Wait. / Installing Oblix NetPoint 6.1 COREid Server... Please wait.
|------|------|------|------|
0% 25% 50% 75% 100%
||
Committing changes to the Solaris Product Registry
...... DONE
Creating uninstaller...
COREid Server Configuration
Changing file ownership and permissions...
Type 1.
Press Enter. / COREid Server Configuration
Specify the transport security mode between the WebPass/COREid client and the
COREid Server.
[X] 1 - Open Mode: No Encryption
[ ] 2 - Simple Mode: Encryption through SSL and a Public Key Certificate
[ ] 3 - Cert Mode: Encryption through SSL and a Public Key Certificate
To select a choice enter its number, or 0 when you are finished [0]: 1
Type the following:
<coreid server instance id>
hm2uxlds02demo
Press Enter.
<coreid server hostname>
hm2uxlds02
Press Enter.
<coreid-webpass port number>
6023 / COREid Server Configuration
Please provide the COREid Server ID, host name, and port number for the COREid Server connection. You must use a unique ID for each COREid Server you install.
COREid Server ID [] hm2uxds02
Host name where the COREid Server is to be installed [] hm2uxds02
Port number the COREid Server listens to [6022] 6023
Type in 1.
Press Enter. / COREid Server Configuration
Is this the first NetPoint COREid Server installation in the network for this LDAP directory server? If it is the first COREid Server you will be guided through screens to setup the Directory Server.
[X] 1 - Yes
[ ] 2 - No
To select a choice enter its number, or 0 when you are finished [0]: 1
Press Enter. / Do you want to setup SSL between the Oblix NetPoint COREid Server and the
Directory Server?
[ ] 1 - Yes
[X] 2 - No
To select a choice enter its number, or 0 when you are finished [0]:
Type 3.
Press Enter. / Configuring COREid Server...
Configure Directory Server
Your directory server needs to be configured with Oblix schema. Oblix can
automatically update the configuration for you. Alternatively, you can
manually update it through the instructions given to you at setup time. Do you
want to automatically configure your Directory Server now?
[X] 1 - Yes, update schema. Oblix Data will be in the User Data Directory.
[ ] 2 - Yes, update schema. Oblix Data will be in a separate Directory.
[ ] 3 - No
To select a choice enter its number, or 0 when you are finished [0]: 3
COREid Server Configuration
Read.
Press q.
Press Enter. / Please read the information below.
ReadMe
Oblix NetPoint 6.1 ReadMe
Document version: 6.0a
------
Contents
------
* NetPoint 6.1 Documentation and Release Notes
* Contacting Oblix
------
NetPoint 6.1 Documentation and Release Notes
------
NetPoint 6.1 documention is posted on the Oblix Customer Care web site.
To reach this site, copy the following URL into your browser's address line:
This is a secure server. If you type in the URL, note that it begins with
NOT
You will be prompted to log in. If you do not have a user name and password,
Press ENTER to read the text [Type q to quit] q
Please press Enter to Continue
Committing changes to the Solaris Product Registry
...... DONE
Review the parameters for correctness.
Press Enter. / The InstallShield Wizard has successfully installed Oblix NetPoint 6.1 COREid
Server. Click Next to continue the wizard.
COREid Server has been configured successfully. Please start your COREid Server
by running /opt/netpointdemo/identity/oblix/apps/common/bin/start_ois_server
program from command line.
COREid Server Setup Information
Transport Security: open
COREid Server Host Name: hm2uxds02
COREid Server ID: hm2uxds02demo
Port Number: 6023
Please press Enter to Continue
This concludes the installation of the COREiD component. Next, install WebPass on the Web Server Instance.
- Creating the Web Server Instance
For the QA environment, this task is handled by the INET team.
The LDAP team requires only a basic Web Server Instance to be created.
Two web servers hm2uxeb04 and hm2uxeb05.
Both these web servers have a EDMZ interface and an IDMZ interface.
The URL for Wepass is - oblixqa.farmersinsurance.com
- Installing Oblix Netpoint WebPass
Oblix Netpoint WebPass is installed on the Web Server Instance.
Use the following parameter values for the installation.
<webpass instance id> / Webpass01<coreid server instance id> / Oblix
<coreid server hostname> / Oblix
<coreid install directory> / /opt/netpoint/webcomponent
<coreid server-webpass port> / 6022
For each of the following steps, follow the instructions in the left column. Parameter values for each installation may not necessarily match exactly the information in the screenshots on the right.
Log onto the Web Server (Windows) via the console as administrator.Start Windows Explorer and expand folders on the left until the installation executable for WebPass can be seen.
Launch the WebPass installation executable.
Click “Next.” /
Click on “Next.” /
Click on “Next.” /
Specify the installation directory:
d:/oblixqa/webcomponent
Click on “Next.” /
Click on “Next.” /
Wait while WebPass installs. /
Ensure the “Open Mode” is selected.
Click on “Next.” /
Enter the following information:
WebPass ID: <webpass instance id>
(webpassqa01)
Hostname where the COREiD Server is installed: <coreid server hostname>
(hm2uxlds02)
Port number the COREiD Server listens to:
(6024) /
Ensure that the “Yes” radio button is selected.
Click on “Next.” /
Type in the path of the web server config directory:
D:\Netscape\Server4\https-oblixqa\config
Click on “Next.” /
Click on “Next.” /
Restart the web server instance.
Click on Start | Control Panel | Services.
Scroll down and select the appropriate web server instance (testoblix).
Click on Stop.
Click on Start. /
Click on “Next.” /
Restart Webserver..
Stop and start the CoreID Server. / On hm2uxds02
/opt/netpointqa/identity/oblix/apps/common/bin/stop_ois_server
/opt/netpointqa/identity/oblix/apps/common/bin/start_ois_server
This concludes the installation of the WebPass component. Next, proceed to the COREiD System Setup.