Oracle Endeca Information Discovery 3.1 has been released. Excited? If you’re working with 3.0 you probably don’t really need to be. So what’s new and improved? Well there’s a fair bit, some is improved, some may be more nuisance, but I’ll dig into those things next posting. For now how do you install everything?
If you’ve already gone through the installation of 3.0 then you should be familiar with all the steps to configure with WebLogic or Tomcat. If not read my earlier posting on how to install OEID 3.0 for WebLogic, the steps for 3.1 are almost identical.
#1- Uninstall OES version 7.5
The first step is to uninstall Oracle Endeca Server. On my Windows box this was the following command, including the path to where JRE was installed:
C:\Oracle\Middleware\EndecaServer7.5.1_1\oui\bin>setup.exe –deinstall –jreLoc C:\Java\jrockit-jre1.6.0_37-R28.2.5
Next remove the domain from WebLogic. This involves nothing more than stopping WebLogic, removing the entry for your OES domain from the file C:\Oracle\Middleware\domain-registry.xml, and then deleting the folder it referenced.
If you’ve set up a Windows service to automatically start OES make sure you stop and disable it. Forgetting this step may cause you system stability problems.
#2- Install OES version 7.6.0
Run the setup command from whatever folder you extracted the “disk1” files to, again specifying your JRE install path.
setup.exe –jreLoc C:\Java\jrockit-jre1.6.0_37-R28.2.5
Next create the weblogic domain by executing the following file. Note the steps are the same as per 3.0 so just follow the prompts.
Oracle has provided a sample data domain called “Sales History”. You can import this to have a set of data immediately compatible with OEID 3.1 & OES 7.6. I found some issues with accessing this data store because it didn’t appear to have default data sets defined. More on that later, meantime you may find it easier to update the LoadData.grf from the Getting Started project that came with OEID 3.0. That involved nothing more complicated than creating the data domain through the endeca-cmd utility and updating the graph in Integrator to specify “Base” as the Collection key. You will need to have upgraded Integrator first.
#3- Upgrade Integrator
Run the uninstall for Integrator 3.0 and then the install for Integrator 3.1. The install requires you to specify the path to the Eclipse package file, this is a bit of a nuisance compared to the 3.0 installation. You also need to make sure it’s the IDE for Java Developers Indigo version.
If you don’t have the right eclipse package you will be advised that the RSE installation failed and you should check your internet connection. Very likely your internet connection is fine, so instead check your version of Eclipse. The file that worked for me was “eclipse-java-indigo-SR2-win32-x86_64.zip”.
#4- Upgrade Studio
This part gets more complicated, if you forget the fact I went through a half dozen versions of Eclipse before I resolved my “Internet Connection errors”.
If you have content you may want to backup up your existing install. Then just remove the domain from WebLogic in the same way we did the OES domain.
As before run this file to recreate the domain:
“Basic WebLogic Server Domain” is the one you want and will be selected by default. The process is pretty straight forward as you go through each of the steps. When you get to the “Select Optional Configuration” just make sure to select “Administration Server”. This will let you change the listening port so you don’t conflict with OES listing on port 7001 already.
In the domain folder create these additional folders (<studio_domain> is whatever name you picked):
..\user_projects\domains\<studio_domain>\eid\studio\data\endeca-data-sources ..\user_projects\domains\<studio_domain>\eid\studio\deploy ..\user_projects\domains\<studio_domain>\eid\studio\weblogic-deploy
Extract and copy the file “portal-ext.properties” to the ..\eid\studio\ folder.
Logon to http://localhost:8101/console (replace 8101 with whatever port you specified earlier). Import the file “endeca-portal-weblogic-3.1.14220.ear”. These steps are the same as they were for installing OEID 3.0.
Once you finish remember to make sure your application is started. And to access it be aware the path is now http://localhost:8101/eid (again that may not be your port number). The default login is still firstname.lastname@example.org and “Welcome123”.
You won’t be able to do much until you have data to work with, so your first step to run Studio will need to be creating some data sources.
#5 – Upgrade Provisioning Services (optional)
This process is also pretty much the same as it was for OEID 3.0. Remember to remove the old provisioning service domain folder and its corresponding reference in the file: “C:\Oracle\Middleware\domain-registry.xml”. Also remove the old provisioning service application folder (..\user_projects\applications\<old_prov_service>).
When you get to the “Select Optional Configuration” select “Administration Server”. In my case the port was already set to 8201 and wasn’t defaulting to 7001, but better to check to be sure. Also verify the ws port is 7001 in the file: “..\user_projects\domains\prov_domain\eidProvisioningConfig\plan.xml”
Note if you’re running an SSL environment those ports would default to 8202 and 7002 respectively.
Once you start the service you should be able to verify it through a browser.
You’ll have to update the JSON entry for Provisioning Service in the Control Panel before you can use the service.
So you should now be up and running and able to start checking out OEID 3.1 for yourself.