So this week some guy came to me almost in panic because his project had a requirement that was not properly addressed.
In our infrastructure we had Oracle HTTP Server 22.214.171.124 and as I could see, TLS v1.2 was NOT supported in this version.
We had two options:
- Upgrade to 126.96.36.199
- Install 12.2.1 on another server
As we’re begining to migrate everything to 12c, I thought it was a great opportunity to install something from scratch, this time, the proper way.
So let’s get started.
First, you must get these two files:
These are available on Oracle’s website or ODC (Oracle Delivery Cloud – Formerly EDelivery).
Also, you must set up your JAVA environment properly. At the time of writing, and according to the compatibility matrix, 1.8.0u77 was certified for FMW 12.2.1, but you can always change this to a newer JDK.
[oracle@oracle staging]$ cd /u01/staging/
[oracle@oracle staging]$ java -jar fmw_188.8.131.52.0_infrastructure.jar
Don’t forget to run createCentralInventory.sh as root!
[root@oracle ~]# sh /home/oracle/oraInventory/createCentralInventory.sh
Setting the inventory to /home/oracle/oraInventory
Setting the group name to oinstall
Creating the Oracle inventory pointer file (/etc/oraInst.loc)
Changing permissions of /home/oracle/oraInventory to 770.
Changing groupname of /home/oracle/oraInventory to oinstall.
The execution of the script is complete
Here’s the usual welcome screen…
Just skip this. I know noone who uses this…
One of the requirements of my organization is that we must use this standardized path for FMW products. Don’t ask me why, it’s just the way it is ( know it’s not Oracle standard, but I’m just an employee)
In this case, let’s not install the examples.
Don’t worry about the Java version. To speed up things, I used 1.8u101 to speed up things. But when you install this on a “real” environment, please try to make things properly. 1.8u77 was certified as the time of writing.
Just skip this…
It seems were all good, so let’s just click Install and hope everything does well…
Time to get a cup of coffee…
Well it seems the Java version wasn’t a problem (at least for the installation of FMW…).
I just love when it says “… completed successfully.”…
Time to move to the Oracle HTTP Server Installation.
In this tutorial we shall be installing it on top of the same Oracle Home of FMW Infra. Just click “Next”.
Again, skip Auto Updates…
As said before, we will install Oracle HTTP Server on top of FMW Infrastructure.
As we want to manage Oracle HTTP Server through a nice WebLogic FMW EM console, we should select “Collocated HTTP Server”. This is the main reason we installed FMW Infra first.
Go… Go… Go!!!
Just click “Install” and…
Go get something to eat…
So far so good…
Time to move to the Repository Creation Utility…
[oracle@oracle wt]$ ./oracle_common/bin/rcu
Just select “System Load and Product Load”. I had bad experiences in the past with asking other DBA’s to run the scripts…
Just fill up the blanks as per your needs 🙂
After a quick check, let’s just check everything. These schemas are really small by standard, so I’ll install everything, just in case someone asks me to install something else on top of this…
SQL> select tablespace_name, bytes/1024/1024 from dba_data_files d where d.tablespace_name like 'DEV%';
6 rows selected.
Jet’s just keep things simple here…
And I guess we’re all set..
And we’re almost done!…
Now… let’s create the WebLogic domain.
According to the Installation Guide, we are supposed to create a new domain BEFORE installing OHS. I didn’t do this because I got bad results in the past when trying to extend WLS domains. Either way, Oracle says we can also do it this way.
If you check Oracle HTTP Server, some other options are checked. Just make sure you also check “WSM Policy Manager” as this is stated in the FMW Installation Guide.
If this is what you want, click Next.
Be safe, always! 😉
So… I suppose you already know the differences here, so, I’ll leave this up to you.
Im my case, I’m choosing Production.
Just fill the blanks again… Don’t forget to click “Get RCU Configuration” to make sure you can get the RCU info.
If these are the schemas you created earlier and the passwords are all the same, click “Next”.
Make sure everything is green…
As we are installing HTTP Server, we don’t need to create a Managed Server, as HTTP Server is a component that runs outside WLS. In this case I’m checking “Topology” because I want to create one to try something later. — But you don’t have to!
Also, don’t forget to check “System Components”, as this is the option that will create a new ohs instance for you.
Make sure you’re not listening on “Localhost” or “All addresses”. This is often not a good idea.
I usually want to keep things simple…
Here you can create a new managed server. If this is the case, be sure you assign it a proper listen address.
I’m not creating clusters now. I’ll leave this for some other day
… but there’s Coherence, so accept the default port (if unassigned, of course).
Add a node manager to your machine.
Don’t forget to assign the managed server(s) to the machine you just created.
And Click Next again…
Here’s the part we create the HTTP Server component.
And here’s where we configure it.
Again, we’re assigning the OHS component to the machine we created.
And go get more coffee…
Finally we’re done configuring and installing stuff…
Time to start the AdminServer and the NodeManager.
If you opted for the Production installation, don’t forget to create a boot.properties file.
Start the nodeManager first so that the Admin Server has a clean start…
[oracle@oracle ~]$ cd /wbldsk/fmw/wt/user_projects/domains/wt_domain/bin/
[oracle@oracle bin]$ nohup ./startNodeManager.sh &
And now, fire up the famous startWeblogic.sh script…
[oracle@oracle bin]$ cd /wbldsk/fmw/wt/user_projects/domains/wt_domain/
[oracle@oracle wt_domain]$ nohup ./startWebLogic.sh &
And enjoy the new FMW EM screens…
Have a nice day… 🙂