Discoverer Patch set upgrade from 11.1.1.X to 11.1.1.6

Installing discoverer Patchset 6

To install patchset 6   Jdk1.6.0.21  and weblogic 10.3.2 need to be upgrade to weblogic 10.3.6 or 10.3.7

1. Install jdk  :

Download jdk-6u21-linux-x64.bin and install

sh  jdk-6u21-linux-x64.bin

Example:

=======

sh  jdk-6u21-linux-x64.bin

Creating jdk1.6.0_21/jre/lib/rt.jar

Creating jdk1.6.0_21/jre/lib/jsse.jar

Creating jdk1.6.0_21/jre/lib/charsets.jar

Creating jdk1.6.0_21/lib/tools.jar

Creating jdk1.6.0_21/jre/lib/ext/localedata.jar

Creating jdk1.6.0_21/jre/lib/plugin.jar

Creating jdk1.6.0_21/jre/lib/javaws.jar

Creating jdk1.6.0_21/jre/lib/deploy.jar

Java(TM) SE Development Kit 6 successfully installed.

Product Registration is FREE and includes many benefits:

* Notification of new versions, patches, and updates

* Special offers on Sun products, services and training

* Access to early releases and documentation

Product and system data will be collected. If your configuration

supports a browser, the Sun Product Registration form for

the JDK will be presented. If you do not register, none of

this information will be saved. You may also register your

JDK later by opening the register.html file (located in

the JDK installation directory) in a browser.

For more information on what data Registration collects and

how it is managed and used, see:

http://java.sun.com/javase/registration/JDKRegistrationPrivacy.html

Press Enter to continue.....

Done.

2.  Installing weblogic 10.3.6

Review the certification note 1064633.1

Login to discoverer node as disco user

Start the VNC

$ echo $DISPLAY

$ export DISPLAY=localhost:<VNC port>

$cd <MIDDLEARE_HOME>/wls_103/

$ls –l  (check the directory permission to avoid error during upgradefor permission denied)

$ chmod –R 755 * for all files

Download patch p11060985_1034_Generic.zip

Command to upgrade weblogic :

$ /tsenzi/disco11g/product/jdk1.6.0_21/bin/java Djava.io.tmpdir=/tsenzi/disco11g/tmp -jar/autofs/ohsarch/ohsinit/disco_11116/weblogic_1036/wls1036_upgrade_generic.jar -log=wl1036.log

Screen 1

Select Use an existing Middleware Home

Click Next

 Screen2

Uncheck the I wish security check box and click Yes

Screen 3

Click Yes

Screen 4

Click Yes

Note : you Need to wait 5 minute before the next screen comes up.

Screen 5:

Click next

Screen 6:

Run the script root.sh as root and click ok   and then when the finish button gets activated click finish

2.1  Check the weblogic version:

$ cd <MIDDLEWARE_HOME>/wls_103

$ grep WLS_PRODUCT_VERSION .product.properties

WLS_PRODUCT_VERSION=10.3.6.0

3.   Apply discoverer patchset6 to upgrade  to 11.1.1.6

Download and Start the Patch Set Installer

Check the central inventory pointing to correct location and group.

Or else we can use invPtrLoc to use the local inventory

11.1.1.6  patch set : p13517084_111160_Linux-x86-64.zip

Unzip the patch and go to Disk1

cd  <PATCHLOCATION>/Disk1

Start the installer:

On UNIX operating systems:

./runInstaller

Screen 1

Welcome screen, Click on Next

Screen 2

Choose Existing Middleware Home , Click on Next

Screen 3

Installation Summary=> Click on Install

Here you may get the error: Patchset in Silent Mode it fails with "MYORACLESUPPORT_USERNAME(MyOracleSupportUsername)"

Solution:

Rename $ORACLE_HOME/ccr/bin/emCCR to emCCR_LAST and Try again

Screen 4

Installation Progress Screen, Monitor the Installtion

Screen 5

Run root.sh as root user

Once the installer is completed .

Check the version of disco:

$ cd $ORACLE_HOME/bin;strings -a dis51ws | grep -i 'Discoverer Version'

Discoverer Version:Server 11.1.1.6.0

Post-Patching task for System Components

Reference: http://download.oracle.com/docs/cd/E17904_01/doc.1111/e16793/patch_set_installer.htm

4. Upgrading System Components

Start weblogic and discoverer11g

Adminserver start:

nohup sh /tsenzi/disco11g/product/user_projects/domains/tsenzi/bin/startWebLogic.sh -Dweblogic.management.username=weblogic -Dweblogic.management.password=welcome1 > /tsenzi/disco11g/product/user_projects/domains/tsenzi/wls_start.log &

tail –f  /tsenzi/disco11g/product/user_projects/domains/tsenzi/wls_start.log

Node manager start:

cd /tsenzi /disco11g/product/wls_103/server/bin

$ nohup ./startNodeManager.sh &

Sart Managed Server:

On browser go to the admin server URL

URL= http://<URL>:40x01/console    where x stand for 7, 5 or 0  depending on the instance

Username = weblogic

Password = welcome1

On the left hand pan expand Environment

Click servers -   (it may take some time to bring the next page)

On the right handside click the control tab.

 select WLS_DISCO click on start -  then click yes

The status will show STARTING  it may take time to start.

Refresh the page by clicking on servers

Once the status change to RUNNING

Start  Disco services:

$ opmnctl startall

opmnctl startall: starting opmn and all managed processes...

$ opmnctl status

Processes in Instance: disco_111

---------------------------------+--------------------+---------+---------

ias-component                    | process-type       |     pid | status 

---------------------------------+-----------------------------+---------

emagent_disco_111                 | EMAGENT            |   18265 | Alive  

Discoverer_disco_111             | PreferenceServer   |   18264 | Alive  

Discoverer_disco_111             | ServicesStatus     |   18261 | Alive  

webcache1                                | WebCache-admin     |   18263 | Alive  

webcache1                                | WebCache           |   18262 | Alive  

ohs1                                          | OHS                |   18260 | Alive    

Upgrading System Components:

$echo $ORACLE_HOME (The ORACLE_HOME environment variable has been set to your product's Oracle home directory)

cd $ORACLE_HOME/opmn/bin

To run the script on UNIX operating systems:

cd ORACLE_HOME/opmn/bin

./upgradenonj2eeapp.sh

   -oracleInstance <Instance_Home_Location>

   -adminHost <WebLogic_Server_Host_Name>

   -adminPort <administration_server_port_number>

   -adminUsername <administration_server_user>

Sample out put :

$ ./upgradenonj2eeapp.sh -oracleInstance /dsmu2i/disco11g/product/instance adminHost auohstest55 -adminPort 42701 -adminUsername weblogic

Unregister instance...

Command requires login to weblogic admin server (auohstest55):

  Username: weblogic

  Password:

Unregistering instance

Command succeeded.

redeploy NonJ2EEManagement.ear...

Command requires login to weblogic admin server (auohstest55):

  Username: weblogic

  Password:

Redeploying NonJ2EEManagement Application...weblogic.Deployer invoked with options:  -adminurlauohstest55:42701 -username weblogic -name NonJ2EEManagement -source /dsmu2idisco11g/product/disco_111/opmn/applications/NonJ2EEManagement.ear -redeploy -upload -noexi

<Jun 2, 2011 5:41:04 PM CDT> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating redeployoperation for application, NonJ2EEManagement [archive: /dsmu2idisco11g/product/disco_111/opmn/applications/NonJ2EEManagement.ear], to configured targets>

Task 0 initiated: [Deployer:149026]deploy application NonJ2EEManagement [Version=11.1.1] onAdminServer.

Task 0 completed: [Deployer:149026]deploy application NonJ2EEManagement [Version=11.1.1] onAdminServer.

Target state: redeploy completed on Server AdminServer

Done

Command succeeded.

re-register instance...

Command requires login to weblogic admin server (auohstest55):

  Username: weblogic

  Password:

Registering instance

Command succeeded.

Successfully upgraded NonJ2EEManagement.ear and the registeration.

$

Updating Fusion Middleware Shared Libraries

For each WebLogic Server domain, you must run the updateJRF() WLST command to update the shared libraries in your domain:

Note:

If you are patching Oracle WebCenter, you do not need to run this command.

Step 1:

Stop all running instances, Managed Servers, Administration Server, and Node Manager in the domain. See section

9.9 Stop and start discoverer services

Step 2:

$ cd /dsmu1i/disco11g/product/utils/config/10.3
$ cp -p setHomeDirs.sh setHomeDirs.sh_jun21_orig
$ vi setHomeDirs.sh

change From

MW_HOME="@MW_HOME"
WL_HOME="@WL_HOME"
To
MW_HOME="$MW_HOME"
WL_HOME="$WL_HOME"
~

Save the file.

$ cd /tsenzi/disco11g/product/oracle_common/common/bin

export MW_HOME=/tsenzi/disco11g/product

$ . ./setHomeDirs.sh

$ env | grep COMMON_COMPONENTS_HOME

COMMON_COMPONENTS_HOME=/dsmu2i/disco11g/product/oracle_common

$ . ./setWlstEnv.sh

$ ./wlst.sh

wls:/offline>

At  wls:/offline>  prompt  enter the following comment

upgradeJRF('/tsenzi/disco11g/product/user_projects/domains/tsenzi')

Output:

upgradeJRF: BEGIN

Apply patch template

Create Library "adf.oracle.businesseditor#1.0@11.1.1.2.0"

Target Library "adf.oracle.businesseditor#1.0@11.1.1.2.0" to JRF "AdminServer"

Target Library "adf.oracle.businesseditor#1.0@11.1.1.2.0" to JRF "WLS_DISCO"

Create Library "oracle.adf.desktopintegration.model#1.0@11.1.1.2.0"

Target Library "oracle.adf.desktopintegration.model#1.0@11.1.1.2.0" to JRF "Admi

nServer"

Target Library "oracle.adf.desktopintegration.model#1.0@11.1.1.2.0" to JRF "WLS_

DISCO"

Create Library "oracle.adf.desktopintegration#1.0@11.1.1.2.0"

Target Library "oracle.adf.desktopintegration#1.0@11.1.1.2.0" to JRF "AdminServe

r"

Target Library "oracle.adf.desktopintegration#1.0@11.1.1.2.0" to JRF "WLS_DISCO"

Target Library instances from sub-templates:

Target Library "oracle.bi.adf.model.slib#1.0@11.1.1.2.0" to JRF "AdminServer"

Target Library "oracle.bi.adf.model.slib#1.0@11.1.1.2.0" to JRF "WLS_DISCO"

Target Library "oracle.bi.adf.view.slib#1.0@11.1.1.2.0" to JRF "AdminServer"

Target Library "oracle.bi.adf.view.slib#1.0@11.1.1.2.0" to JRF "WLS_DISCO"

Target Library "oracle.bi.adf.webcenter.slib#1.0@11.1.1.2.0" to JRF "AdminServer

"

Target Library "oracle.bi.adf.webcenter.slib#1.0@11.1.1.2.0" to JRF "WLS_DISCO" Target Library"oracle.bi.jbips#11.1.1@0.1" to JRF "AdminServer"

Target Library "oracle.bi.jbips#11.1.1@0.1" to JRF "WLS_DISCO"

Target Library "oracle.bi.composer#11.1.1@0.1" to JRF "AdminServer"

Target Library "oracle.bi.composer#11.1.1@0.1" to JRF "WLS_DISCO"

Create StartupClass "Web Services Startup Class"

Target StartupClass "Web Services Startup Class" to JRF "AdminServer"

Target StartupClass "Web Services Startup Class" to JRF "WLS_DISCO"

Set DiagnosticContextEnabled for server "AdminServer"

Set DiagnosticContextEnabled for server "WLS_DISCO"

Copy JRF configuration files from /dsmu2i/disco11g/product/oracle_common/modules

 to /dsmu2i/disco11g/product/user_projects/domains/dsmu2i/config/fmwconfig/serve

rs/AdminServer

Copy JRF configuration files from /dsmu2i/disco11g/product/oracle_common/modules

 to /dsmu2i/disco11g/product/user_projects/domains/dsmu2i/config/fmwconfig/serve

rs/WLS_DISCO

upgradeJRF: FINISH

wls:/offline>exit ()

Exiting WebLogic Scripting Tool.

Enabling WS-AtomicTransaction

WS-tomicTransaction is a web services features which was introduced in Oracle Fusion Middleware Release 11.1.1.3.0 release. If you are upgrading a domain which is at the 11.1.1.2.0 release, then you need to perform the following steps to ensure that WS-AtomicTransactions are enabled:

edit the following file.

On UNIX operating systems:

$DOMAIN_HOME/config/fmwconfig/policy-accessor-config.xml

In the Interceptors section, add the following XML code:

<interceptor name="ClientWSATInterceptor”

   class="oracle.j2ee.ws.client.transaction.ClientWSATInterceptor"

   category="transaction" />

<interceptor name="ServerWSATInterceptor”

   class="oracle.j2ee.ws.server.transaction.ServerWSATInterceptor"

   category="transaction" />

In the Interceptor Chains section:

<interceptor-ref name="ServerWSATInterceptor"/> should be added in the existing entry of SOAPServiceBindingInterceptorChain between the Context and RM interceptors. For example:

<interceptor-chain name="SOAPServiceBindingInterceptorChain"

@ class="oracle.integration.platform.common.SOAPBindingInterceptorChain">

         <interceptor-ref name="MTOMInterceptor"/>

         <interceptor-ref name="BindingSecurityInterceptor"/>

         <interceptor-ref name="ServerAddressingInterceptor"/>

         <interceptor-ref name="MEXInterceptor"/>

         <interceptor-ref name="WSRMServerInterceptor"/>

<interceptor-ref name="ServerWSATInterceptor"/>

         <interceptor-ref name="ContextInterceptor"/>    

         <interceptor-ref name="BindingManagementInterceptor"/>

</interceptor-chain> 

<interceptor-ref name="ClientWSATInterceptor"/> should be added in the existing entry of SOAPReferenceBindingInterceptorChain between the Context and RM interceptors. For example:

<interceptor-chain name="SOAPReferenceBindingInterceptorChain"

@ class="oracle.integration.platform.common.SOAPBindingInterceptorChain">

         <interceptor-ref name="BindingManagementInterceptor"/>

         <interceptor-ref name="ContextInterceptor"/>

<interceptor-ref name="ClientWSATInterceptor"/>

         <interceptor-ref name="WSRMClientInterceptor"/>

         <interceptor-ref name="ClientAddressingInterceptor"/>

         <interceptor-ref name="BindingSecurityInterceptor"/>

         <interceptor-ref name="MTOMInterceptor"/>

</interceptor-chain>

Set Applications Profile Options for Discoverer using AutoConfig

Login as  aptsenzi

$ grep s_disco_url $CONTEXT_FILE

Make sure the value is correct

<protocol>:// machine.domain>:<port>

If not edit the context file and correct the value.

Set Applications profile options in Oracle E-Business Suite

Log into E-Business Suite Release 12 with the System Administrator responsibility

Navigate to the Profile > System form

Query the %Discoverer% profile options.

Profile Description Value

ICX: Discoverer Launcher :   URL that points to Discoverer Plus Servlet.

http://<HTTP Server>:<Port>/discoverer/plus?Connect=[APPS_SECURE]

ICX: Discoverer Viewer Launcher :  URL that points to Discoverer Viewer Servlet

http://<HTTP Server>:<Port>/discoverer/viewer?Connect=[APPS_SECURE]

ICX: Discoverer use Viewer:

Specify whether Discoverer Viewer should be launched instead of Discoverer Plus (default).

Yes | No

ICX: Discoverer Default End User Layer Schema Prefix

The EUL prefix in combination with the Language code make up the EUL owner at runtime. For example EUL owner EUL_US has EUL prefix EUL.

You may switch the ICX_DEFAULT_EUL profile at the responsibility level if you are planning to implement multiple End User Layers.

EUL

 ICX: Discoverer End User Layer Language Override

Since the End User Layer content is currently available in US English only, it is possible to override the user's general language preference for the Discoverer End User Layer using this profile option. The specified End User Layer language will be used regardless of the individual user's language preferences.

This profile does not affect the National Language Support parameters passed to Discoverer. The Discoverer User Interface will still appear according to the users ICX_LANGUAGE and ICX_TERRITORY profiles. The User Interface language will only change for valid combinations of ICX_LANGUAGE and ICX_TERRITORY. American English.

 ICX: Discoverer Release
Single number specifying the Discoverer release.

Leave this at default value <NULL> as there is no difference in invocation of the two supported Discoverer releases 10g and 11g for E-Business Suite Release 12.

11

ICX: Discoverer Parameters

This profile can be used to optionally pass additional URL parameters to Discoverer.

exitURL=<E-Business Suite Home Page>

For Example

exitURL=http://<HTTP Server>:<Port>/OA_HTML/OA.jsp?OAFunc=OAHOMEPAGE

Discoverer DBC filename override
This profile can be used to specify the DBC Filename Discoverer should be using to connect to the E-Business Suite database.

By default, this profile should remain NULL, in which case Discoverer will use the default dbc file for your E-Business Suite database.

<NULL>

Verification & Pre-Release Steps

Discoverer 11g :

$ echo $ORACLE_HOME

/tsenzi/disco11g/product/disco_111

$ cd $ORACLE_HOME/bin;strings -a dis51ws | grep -i 'Discoverer Version'

Discoverer Version:Server 11.1.1.4.0

Weblogic:

$ cd $WL_HOME;grep WLS_PRODUCT_VERSION .product.properties

WLS_PRODUCT_VERSION=10.3.4.0

Cloning issue from SSL to Non SSL Enabled E-Business Suite Middle Tier

The Rapidclone utility does not support like for like cloning of an SSL enabled E-business suite middle tier.
Note 230672.1 Cloning Oracle Applications Release 11i with Rapid Clone
Note 406982.1 Cloning Oracle Applications Release 12 with Rapid Clone

The problem can be broken down into 3 issues

1:- File system changes.

The location of the SSL files on the clone is different to that from the source. From the bug we can see the following were not the same between source and target.


For 11i

s_frmWalletDir
s_web_ssl_directory
s_web_ssl_keyfile
s_web_ssl_certfile
s_web_ssl_certchainfile


For R12

s_url_protocol
s_local_url_protocol
s_webentryurlprotocol
s_active_webport
s_webssl_port
s_https_listen_parameter
s_help_web_agent
s_login_page
s_external_url

2:- SSL Port is wrong in the clone.

s_webssl_port - Gets Defaulted to 443, ideally it should take Apache Port given during adcfgclone run.

3:- SSL certificates are the same on the clone as they are on source.

This might be a security issue depending on your security requirements.

However Rapidclone will create a clone of an SSL enabled middle tier, but the target will require additional configuration to allow it to function correctly. To progress the issue further you must decide if

A:- You want the middle tier clone to be SSL enabled.

Re-implement SSL on the clone following the note below.

Note 123718.1 11i: A Guide to Understanding and Implementing SSL for Oracle Applications

Note 376700.1 Enabling SSL in Oracle E-Business Suite Release 12

B:- You want the middle tier clone to be HTTP only.

Remove the SSL configuration added in

Note 123718.1 11i: A Guide to Understanding and Implementing SSL for Oracle Applications

Note 376700.1 Enabling SSL in Oracle E-Business Suite Release 12

R12: Relink error for MSC modules

Cause

The following packages are not part of the Oracle Linux 5*  distribution media and must be downloaded separately and installed manually:

For Update 1 or 2:
binutils-2.17.50.0.6-6.0.1.x86_642

For Update 3:
binutils-2.17.50.0.6-9.0.1.x86_642

For Update 4 (5.4) or higher, there is workaround for failures while relinking the Advanced Supply Chain Planning (ASCP) executables MSO, MSC, MSR and FEM.

Solution

To fix this problem, users are required to replace the following line under the Linux section of file " $AD_TOP/bin/adrelinknew.sh":

From:

CPP_LDFLAGS=' -L$(ORACLE_HOME)/lib -L$(ORACLE_HOME)/lib/stubs -lclntsh'

TO:

CPP_LDFLAGS=' -L$(ORACLE_HOME)/lib -L$(ORACLE_HOME)/lib/stubs -lclntsh -Wl,--noinhibit-exec'

After making this change, run adadmin utility to relink MSC product.

Explanation

--noinhibit-exec
 Retain the executable output file whenever it is still usable.  Normally, the linker will not produce an output file if it encounters errors during the
link process; it exits without writing an output file when it issues any error whatsoever.

Binutils developers apparently have a very relaxed definition of usable,
because this option can lead to binaries that are very unusable without
advanced hackery.