Why Soup to Nuts?
I was looking at my statistics on my most visited pages, and the entries on Discoverer 11g installation and Enterprise Manager 11g installation are by far tops. I was using my own entries as a guide to re-install Discoverer 11g the other day (it needed to be relocated to a new server) and I realized it was a bit confusing, with important information in several different posts.
What’s New?
Details regarding how to change the default Discoverer 11g client timeout (60 mins), how to install Discoverer on a 64-bit platform, and applying the January 2011 CPU. Other than that, I’m mostly just smoothing wrinkles in the walk through, and putting it all in one place. I’m not going to detail 11.1.1.2 as it’s just a subset of 11.1.1.3 and you can find the information elsewhere on the blog.
Environment Variables/Paths I reference
MIDDLEWARE_HOME=Middleware Install Location (xxx/xxx/xxx/Middleware)
DOMAIN_HOME=$MIDDLEWARE_HOME/user_projects/domains/ClassicDomain
WL_HOME=$MIDDLEWARE_HOME/wlserver_10.3
ORACLE_HOME=Middleware/as_1
ORACLE_INSTANCE=Middleware/asinst_1
Step 1: Weblogic
The first step is to determine, download and install the appropriate version of WebLogic server. According to my Oracle technology salesperson (as opposed to the 11i Apps salesperson), this is free as we are paying for Discoverer. I encourage you to check your license terms before you assume you’re entitled to this product, as much has changed since the “old days” of 4i.
You can find the downloads at http://www.oracle.com/technetwork/middleware/weblogic/downloads/wls-main-097127.html Note, my experience is only installing on Linux, but I’ve done both 32-bit and 64-bit installs so I can go through those. This is by far the easiest part of the whole install.
Ensure that your WebLogic version lines up with your planned Discoverer install
Oracle Fusion Middleware 11.1.1.3.0 is certified (only) with WebLogic Server 10.3.3 and Apps 11i
If you’re running the 32-bit installer, you just execute the downloaded .bin file; it contains java already and is an executable binary. If you’re installing the 64-bit version, you’re getting a jar file which isn’t platform specific. You need to start the installer by using syntax: java -jar wls1033_generic.jar or the like.
There’s really nothing to the install. I went with defaults, although I’m not sure I needed Oracle Coherence, I figured it wasn’t worth the effort of researching it much further. There’s only one last item of note here: uncheck and don’t run the quickstart when it’s done laying down the files.
Finally, if you screw up, don’t like the install location, or change your mind, there’s an oui uninstaller buried in there somewhere. That still leaves a mess on the filesystem (and inventory, in my experience) so the other option is to rm -rf the whole install directory and clean up the oracle inventory ($INVENTORY_HOME/oraInventory/ContentsXML/inventory.xml) to remove references to the install you just did.
That’s it. Check the box, you’re done with the WLS install for now. Once all the pieces are installed, there’s a few critical files you may wish to manually edit (regarding starting services) but I’ll go over that later.
Step 2: Discoverer Fusion Installation
Once again, you need to pull the install for the appropriate version of Discoverer. You can find the downloads at http://www.oracle.com/technetwork/middleware/downloads/fmw-11-download-092893.html towards the bottom of the page.
Since I’m only concerned with 11.1.1.3, pull Portal, Forms, Reports and Discoverer (11.1.1.2) and Portal, Forms, Reports and Discoverer (11.1.1.3). The 11.1.1.3 installer is only an upgrade from 11.1.1.2, so you have to run both of them. Note that there’s also the Windows-only Discoverer Desktop and Discoverer Administrator (11.1.1.3) which you will probably need, as well as the Repository Creation Utility (RCU) 11.1.1.3.3.
Start with the Fusion Middleware (FMW) 11.1.1.2 install. Simply run the installer and follow the bouncing ball, but ensure you select software only install. There’s no sense trying to configure 11.1.1.2, you’re not going to use it. When it’s done, run the 11.1.1.3 installer.
I don’t recall which installer (11.1.1.2 or 11.1.1.3) asks for what, but here’s what’s of note during the questions it asks.
- It will want to know where your Fusion Middleware home is. Point it to the WLS 10.3.3 install home.
- Remember the password you provide for the weblogic user, it’s important
- Stick with the defaults, unless you’re an experienced Weblogic user, regarding Oracle Home name (as_1), Oracle Instance name (asinst_1), and the domain name (ClassicDomain).
- Under components to install, uncheck everything except Oracle Discoverer and Web Cache. Note there’s a checkbox for Clustered there also. I unchecked it, have no idea what checking it leads to but it wasn’t applicable to me.
At this point, both installers should be done, but nothing should be configured.
Step 3: Repository Creation Utility (RCU)
The RCU just creates a few tablespaces, new users, and objects in the database. I don’t know for certain if it uses your existing repository, but it seems that it does. To launch the RCU, unzip the file, and run the executable called rcu which is in the bin directory.
Of note to the questions it asks:
- The only thing you need checked on the entire Select Components screen is Discoverer. (Under Portal and BI-> Discoverer)
- Remember your new schema user and passwords, they will be required during the configuration of Discoverer and Weblogic. I recommend SID_DISCOVERER (PROD_DISCOVERER)
Step 4: Configuration
Now you will need to run $MIDDLEWARE_HOME/as_1/bin/config.sh to complete the Discoverer setup.
Most of this should be easy to answer by now, but of note are a few things:
- Under Specify Schema, use the SID_DISCOVERER (PROD_DISCOVERER) schema you set up with the RCU
- Unless you’re using OID, uncheck Use Application Level Identity Store. I missed this once (I don’t use OID) and troubleshooting the startup was impossible. I had to reinstall the whole stack.
- I recommend using Auto Port configuration if possible
- At the end of the config.sh GUI, it displays all ports and URLS. I recommend you save this file to the OS as it’s a handy reference for how to get to the WLS server and Discoverer login page.
- Follow note 1073963 which details some profile option values which you need to change in 11i to accommodate Discoverer 11g.
Step 5: Fixes
1. Fix the webcache bug (doc 1113163.1) “Failed to assign port 8090: Address family not supported by protocol”if you hit it
- Edit the file $MIDDLEWARE_HOME/asinst_1/config/WebCache/webcache1/webcache.xml
- Add <IPV6 ENABLED=”NO”/> tag below the </MULTIPORT> tag
2. I also hit a common webcache problem this time, where the webcache wouldn’t start because webcached permissions hadn’t been set right:
- Navigate to $MIDDLEWARE_HOME/as_1/webcache/bin
- As root, run webcache_setuser.sh setroot (username) where username is the user who installed the webcache
- Permissions should look like this when you’re done: -rwsr-x— 1 root dba 6796777 Dec 3 11:32 webcached
3. Copy/link the approriate (8.0.6 home for 11i installs) tnsnames. ora file to 2 locations with a command like this (substitute cp for ln if you want to simply copy the file, obviously)
- cd $MIDDLEWARE_HOME/asinst_1/config
- ln -s $8.0.6_HOME/network/admin/SID_host/tnsnames.ora
- cd $MIDDLEWARE_HOME/as_1/network/admin4
- ln -s $8.0.6_HOME/network/admin/SID_host/tnsnames.ora
4. Change the Discoverer default timeout
- Edit the attribution Timeout in ORACLE_INSTANCE/config/PreferenceServer/Discoverer_instance-name/pref.txt
- Run ORACLE_INSTANCE/Discoverer/Discoverer_instance-name/util/applypreferences.sh
5. Hard code your password in the startup/shutdown scripts
- Edit $DOMAIN_HOME/bin/startManagedWebLogic.sh and stopManagedWebLogic.sh
- add entries for:
- WLS_USER=”weblogic”
- export WLS_USER
- WLS_PW=”password”
- export WLS_PW
Step 6: Starting/Stopping
These scripts works great for me. You may have to tweak them a bit, but it’s tested and proven. Note the sleeps are in there because it takes time to crank some of the services, and unless they’re running the next step fails. 60 seconds is generous.
# STARTUP
export MIDDLEWARE_HOME=/u02/appdevl/devdisco/Middleware
export DOMAIN_HOME=$MIDDLEWARE_HOME/user_projects/domains/ClassicDomain
export WL_HOME=$MIDDLEWARE_HOME/wlserver_10.3
export ORACLE_HOME=/u02/appdevl/devdisco/Middleware/as_1
xport ORACLE_INSTANCE=/u02/appdevl/devdisco/Middleware/asinst_1
rm -rf nohup.out
rm -rf /tmp/wls_start.log
rm -rf /tmp/start_nodemanager.log
rm -rf /tmp/start_mgdwls.log
echo “Ensure NO processes related to disco 11g are running or this will fail”
nohup $DOMAIN_HOME/bin/startWebLogic.sh -Dweblogic.management.username=weblogic -Dweblogic.management.password=yourpass > /tmp/wls_start.log &
nohup $WL_HOME/server/bin/startNodeManager.sh > /tmp/start_nodemanager.log &
echo “sleeping”
sleep 60
nohup $DOMAIN_HOME/bin/startManagedWebLogic.sh WLS_DISCO t3://(server.domain):7001 > /tmp/start_mgdwls.log &
echo “sleeping”
sleep 60
$ORACLE_INSTANCE/bin/opmnctl startall
$ORACLE_INSTANCE/bin/opmnctl status
echo “If Discoverer doesn’t start properly, login to http://(server.domain):7001/console”
echo “From the home page, click servers (Under Environment), then the control tab. Check WLS_DISCO then click the start button below the checkbox”
# Shutdown
#!/bin/bash
export MIDDLEWARE_HOME=/u02/appdevl/devdisco/Middleware
export DOMAIN_HOME=$MIDDLEWARE_HOME/user_projects/domains/ClassicDomain
export WL_HOME=$MIDDLEWARE_HOME/wlserver_10.3
export ORACLE_HOME=/u02/appdevl/devdisco/Middleware/as_1
export ORACLE_INSTANCE=/u02/appdevl/devdisco/Middleware/asinst_1
$ORACLE_INSTANCE/bin/opmnctl stopall
$ORACLE_HOME/opmn/bin/opmnctl status
# stop the discoverer server
$DOMAIN_HOME/bin/stopManagedWebLogic.sh WLS_DISCO t3://(server.domain):7001 weblogic password
# stop the weblogic admin server
$DOMAIN_HOME/bin/stopWebLogic.sh
killall startNodeManager.sh
killall nmz
echo “There’s probably still 1 disco process running – ps -ef|grep jrockit and kill it (java)”echo “It’s probably pid:”ps -ef|grep jrockit|cut -c10-15
Step 7 CPU (optional)
I had no problem applying CPU0111 (patch 10233533), though my ORACLE_HOME required a more recent Opatch (patch 6880880) version than the installer provided.
Step 8 Navigation Reference (Default)
URLS:
Discoverer Plus: http://hostname:8090/discoverer/plusDiscoverer
Viewer: http://hostname:8090/discoverer/viewer
Weblogic Server Administration: http://hostname:7001/console
Weblogic Marketing Propoganda: http://hostname:7001
Kevin Kempf's Blog 