Enhancement - Maintenance

Implementation Change

Program Name: <To be created>

Project ID - Name : TRF ID / PTS ID <To be created>

AGS iPlanet migration to Oracle HTTP Server

Document Control
a. Document History

Version Date Status: <Draft Author Comment / Changes from

or Final> Prior Version

1.0 29-Jan-2016 Draft Arun Initial Version

b. Document Reviewers/Approvers 

Name Position (e.g. Client Manager, Project Reviewer Reviewer and

Manager etc.) (only) Approver

Dharmesh Kiyawat AGS Technology Project Manager X

Template Guidelines

Please follow the section guidance that is written in RED.  It is there to assist you in completing the template.

Acquire and Implement Section 2 (AI 2) of the Citi Information Technology Management Standards (CITMS)
specifies the minimum SDLC requirements that must be performed in each project.
These minimum requirements are highlighted in this document template. However it is advised to address all
sections in this document.

If a section is “Not Applicable” please state “N/A” plus a reason why the section does not need to be
addressed. Please remove the RED section guidance as you complete the document.

DOCUMENT PURPOSE
Maintenance Implementation Change template has been designed for use on very small tasks. This document captures
requirements, solution, testing details and release information.
Maintenance Implementation Change Version 2.2
Template Updated 01/14/2015

Copyright © 2015 - Citi

All rights reserved. Information contained herein is for Internal use and may only be used for business purposes authorized
by Citi.
1/19
 CONTENTS
1 REQUIREMENTS............................................................................................................................................................................... 3
Assumptions............................................................................................................................................................................................. 3
Scope........................................................................................................................................................................................................ 4
High-Level Flow Diagram:......................................................................................................................................................................4
2 SOLUTION.......................................................................................................................................................................................... 5
Functional Solution.................................................................................................................................................................................. 5
Technical Solution.................................................................................................................................................................................... 6
Modules Created/Changed/Deleted..........................................................................................................................................................7
3 TESTING PROCEDURES AND TEST RESULTS.............................................................................................................................8
Test Strategy............................................................................................................................................................................................. 8
Entry Criteria............................................................................................................................................................................................ 8
Exit Criteria.............................................................................................................................................................................................. 8
Test Scope................................................................................................................................................................................................ 8
4 RELEASE INFORMATION................................................................................................................................................................8
Installation................................................................................................................................................................................................ 8
Rollback................................................................................................................................................................................................... 9
5 INFORMATION SECURITY - PUMA...............................................................................................................................................9

Page 2 of 19
1 REQUIREMENTS
As the iPlanet reached EOVS, applications which are using iPlanet should be migrated to OHS (version
11.1.1.9). This document covers the technology and architecture changes to be implemented as part of
the iPlanet to OHS (Oracle HTTP Server) migration in CPB AP.

Currently, iPlanet web server being used to host the CA SiteMinder SSO (Single Sign-On) services.

Scope
1) iPlanet instance + Siteminder in AGS Weblogic server (AGS UI) to be migrated as OHS + Siteminder.
Servers in Scope –
Environment Current iPlanet Servers (AIX) New OHS Servers (Linux)
UAT zhcpbuopa1.eur.nsroot.net TBD
Production zhcpbpopa1.eur.nsroot.net TBD

2 Layer Environment
Platform
Current
Hostname Version Platform
Future
Hostname Version
i-planet IST AIX zhcpbpoua1 6.1sp12 RHEL TBD OHS 11.1.1.9
(Weblogic UAT AIX zhcpbpoua1 6.1sp12 RHEL TBD OHS 11.1.1.9
) PROD AIX zhcpbpopa1 6.1sp12 RHEL TBD OHS 11.1.1.9

SOLUTION
Current Vs New Architecture

Page 3 of 19
 Fig.4.1 Current Architecture (iPlanet)

Fig.4.2 New Architecture of OHS (SIT)

Page 4 of 19
Steps for Migration –
1) Shut down all the web logic processes you want to upgrade such as
Node Manager, Admin Server , All Managed Servers.
To ShutDown
Start > All Programs > Oracle Business Intelligence > Stop BI Services and stopped Oracle WebLogic
NodeManager (c_Middleware_wlserver_10.3) service

2) Download JDK1.7 + versions.

3) Download this patch set for weblogic : Patch 13529623.Unzip the file from temproray location and
confirm the extracted contains wls1036_upgrade_generic.jar.

4) Open a Command Window Run as Administrator and run the following command
>java –jar wls11036_upgrade_generic.jar, Upon the execution the installer starts preparing the OUI
install Program.

Page 5 of 19
5) On Choose Middleware Home Directory, select the existing Middleware home you wish to upgrade. Then
Click the next button

Page 6 of 19
6) On Register for Security Updates, the Email address and/or the My Oracle Support Password fields as
applicable. Then click on the next button

7) On Choose Products and Components, verify the components. The OUI installer automatically selects
the Oracle Coherence component. You can choose to select or deselect this component, keeping in mind
that this server type has not yet been verified with Oracle JD Edwards EnterpriseOne.Then Click on the

Page 7 of 19
 next button

8) On Choose Product Installation Directories, verify the directory locations for the previously selected
products and components. A new version of Oracle Coherence_3.7 will be installed.Click on Next Button,

Page 8 of 19
 OUI begins copying the files and performs the upgrade.

9) On Installation Complete, click the check box for Run Quickstart to continue with the upgrade of the
Oracle WebLogic domains. Click the Done button to complete the installation and exit OUI. The
Quickstart configuration screen appears. To manually launch the QuickStart configuration wizard, run this
executable:

<MW_HOME>\oracle_common\common\bin\config.cmd

Page 9 of 19
10) On the QuickStart links panel, select this link:

Upgrade domains to version 10.3.6

An Upgrade Wizard is launched.

Page 10 of 19
11) On the Welcome panel of the Upgrade Wizard, review and complete the tasks listed in
the Prerequisites section of the above screen. When the Prerequisite tasks are complete, click
the Next button

12) On Select WebLogic Version, select this radio button: 9.0 or higher.Click the Next button.

Page 11 of 19
13) On Select a Domain to Upgrade, drill down through
the Oracle\Middleware\user_projects\domains directory structure and select the Oracle JD

Page 12 of 19
 Edwards domain. For example: E1_Apps , Click the Next button.

14) On Inspect Domain, review the upgrade configuration selections., Click the Next button.

Page 13 of 19
15) On Select Upgrade Options, select this check box: Back up current domain (recommended). The
wizard advises you that if you choose the check box or Add log files to backup zip, the resultant zip file
can be extremely large

Page 14 of 19
16) On Domain Backup, review the message. Click the Next button

17) On Select Directory for Domain Backup, you can accept or change location and filename of the backup
zip file. The wizard shows the progress of the domain backup. When the backup is complete, click
the Next button.

Page 15 of 19
18) On Finalize Domain Upgrade, review the message. Click the Next button to begin the Upgrade.

19) On Upgrade Complete, click the Done button to exit OUI. As a result of this domain upgrade, you do not
need to individually upgrade any Managed Server.
20) Start the WebLogic NodeManager. Start the WebLogic Administration Console. Start the existing
Managed Server such as the Oracle JD Edwards EnterpriseOne HTML server. Test and verify the
upgrade.

Page 16 of 19
21)  To check/verify the Weblogic version , Once the server is started you can access the administrator
console using the "http://hostname:7001/console" URL. Log in using the username and
password

22) Run the following command,

java -cp /optional/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar
weblogic.version –verbose

23) In case of the following issue is found,

  Issue: 1

1) After starting Admin server below error is observed:

<<
<Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError:
java.lang.ClassNotFoundException: weblogic.jndi.internal.ServerNamingNode_1035_WLStub 
java.lang.AssertionError: java.lang.ClassNotFoundException:
weblogic.jndi.internal.ServerNamingNode_1035_WLStub 
at
weblogic.jndi.WLInitialContextFactoryDelegate.newRootNamingNodeStub(WLInitialContextFactoryDelegate.ja
va:610) 
at
weblogic.jndi.WLInitialContextFactoryDelegate.newRemoteContext(WLInitialContextFactoryDelegate.java:577) 

at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:482) 
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:376) 

Page 17 of 19
 at weblogic.jndi.Environment.getContext(Environment.java:315) 
Truncated. see log file for complete stacktrace 
Caused By: java.lang.ClassNotFoundException: weblogic.jndi.internal.ServerNamingNode_1035_WLStub 
at java.net.URLClassLoader$1.run(URLClassLoader.java:202) 
at java.security.AccessController.doPrivileged(Native Method) 
at java.net.URLClassLoader.findClass(URLClassLoader.java:190) 
at java.lang.ClassLoader.loadClass(ClassLoader.java:306) 
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) 
Truncated. see log file for complete stacktrace 
> 

Exception in thread "main" java.lang.AssertionError: Failed to load stub for class class
weblogic.server.RemoteLifeCycleOperationsImpl 

>>

Solution:

Step 1) We saw that there is still reference to weblogic.server.modules_10.3.5.0.jar at

location$MW_HOME/modules/features/weblogic.server.modules_10.3.5.0.jar

Step 2) Replace that weblogic.server.modules_10.3.5.0.jar with weblogic.server.modules_10.3.6.0.jar

Step 3) Clean tmp,cache,data and log folder under $DOMAIN_HOME/servers/AdminServer

Step 4) Restart  Admin server

Step 5) Start Node Manager and all manage server (clear tmp,cache,data,log for all manage server).

Issues 2:

http://fusion11g.blogspot.in/2013/09/weblogic-1035-to-1036-error.html

3 TESTING PROCEDURES AND TEST RESULTS

No Test Conditions Actions Expected Results Actual Result Pass/Fail

1 AGS Application UI Login 1) Click AGS Business URL Login should be
2) Provide the Credentials successful and other
and submit the page. screens should work
fine.
3) Traverse the screens for

Page 18 of 19
 sanity check.

4 RELEASE INFORMATION

5 INFORMATION SECURITY - PUMA

Not Applicable.

Page 19 of 19