Oracle Endeca Information Discovery use Provisioning Service to create application based on spreadsheet data where you can upload the sheet and create reports accordingly which will loads on Endeca MDEX engine.
This tutorial explains you configuration of Endeca 3.1 Provisioning Service (Non-SSL) .
The Provisioning Service runs as a web application in a WebLogic Server container you can install on same weblogic where Endeca Server/Studio domains is created .
In order to install and configure Provisioning service make sure that you have below services
1) JDK 1.6
2) weblogic 10.3.6
Note : Before installing Oracle ADF Runtime on Windows, ensure that the path to the location where you have installed the Java JDK is C:\Java, or another path that does not include spaces.
Download below packages from Edelivery.oracle.com (on Windows for Linux it is separate file)
1) EID Provision Service
2) Oracle ADF Downloads
This tutorial explains you configuration of Endeca 3.1 Provisioning Service (Non-SSL) .
The Provisioning Service runs as a web application in a WebLogic Server container you can install on same weblogic where Endeca Server/Studio domains is created .
In order to install and configure Provisioning service make sure that you have below services
1) JDK 1.6
2) weblogic 10.3.6
Note : Before installing Oracle ADF Runtime on Windows, ensure that the path to the location where you have installed the Java JDK is C:\Java, or another path that does not include spaces.
Download below packages from Edelivery.oracle.com (on Windows for Linux it is separate file)
1) EID Provision Service
| Oracle Endeca Information Discovery Provisioning Service (3.1) for Microsoft Windows x64 (64-bit) | V40546-01 | 26M |
2) Oracle ADF Downloads
After you install WebLogic Server, install ADF Runtime 11.1.1.6/11.1.1.7(any one), which contains the JRF needed by the Provisioning Service.
Unzip the file and click on run the setup.exe file from disk1 as shown below
Setup file launches as shown below give the existing weblogic middleware path and leave it as default for the oracle home directory
It will complete in less than 2 minutes once it is done click on Finish.
Running the Provisioning Service installation script:
The Provisioning Service installation script automates the process of creating a WebLogic domain, installing the Provisioning Service, and configuring the Provisioning Service.
Unzip the EID 3.1 Provisioning Service file downloaded from edelivery you should have below three files
- Doc
- eidProvisioningTemplate.jar
- install.py
Open command window and goto the downloaded folder and run below command as shown in screen
- The name of the Provisioning Service domain defaults to endeca_provisioning_service_domain. Press the enter key to accept the default name, or type a new name and press the enter key.
- Enter the name of the WebLogic user for the Provisioning Service domain.
- Enter the password for the WebLogic user for the Provisioning Service domain. The password must include at least eight characters, and one or more of the characters must be a number or special character.
- The non-SSL port of the Provisioning Service defaults to 8201. Press the enter key to accept the default port, or type a new port and press the enter key.
- Enter the host of the Endeca Server. You can enter either the host name or the IP address.
- The default port non-SSL port of Endeca Server is 7001. The default SSL port is 7002. Press the enter key to accept the default, or type a new port and press the enter key.
- When prompted, specify the database configuration for the backend database.The Provisioning Service supports three options for the backend database: Option 2 - Oracle
Once the execution is completed it will automatically exist from WLST
If the database confugraion is failed you can login to the weblogic console http://hostname:8201/console
If you need to configure WebLogic Server to use an Oracle database:
1. Log in to WebLogic Administration Console with the user used to install the Provisioning Service. Lock and edit the Provisioning Service domain.
2. In the Domain Structure box, expand the Services node and click on Data Sources
Administration Console displays the Summary of JDBC Data Sources dialog.
3. Select the jdbc/oracle.eid-ps datasource. Click Delete. WebLogic Server deletes the selected datasource.
4. Create a new datasource with the JNDI name jdbc/oracle.eid-ps.
• For an Oracle database:
(a) Click New and from the drop menu, choose Generic Data Source.
The Administration Console displays the JDBC Data Source wizard.
(b) Enter a Name for the datasource. You can use any name you like.
(c) In the JNDI Name field, enter jdbc/oracle.eid-ps. You must use this name.
(d) In the Database Type drop list, choose Oracle (if you want to use an Oracle database) or
MySQL (if you want to use a MySQL database).
(e) Click Next.
(f) In the Database Driver drop list, choose the appropriate driver for your database.
• If you use an Oracle database, you must use an XA-type driver.
(g) Click Next.
(h) If you specified MySQL, on the Transaction Options page check the Supports Global
Transactions box and select the Logging Last Resource radio button. If you specified Oracle,
take no actions on this page. Click Next.
(i) Enter the hostname ,servicename and database user name and passowrd as shown below
(j) Target the datasource to the Admin Server when asked.
(k) On the Summary of Data Sources page, click on the new jdbc/oracle.eid-ps data source.
Administration Console displays the Settings for jdbc/oracle.eid-ps2 page.
(l) Click the Connection Pool tab. Expand the Advanced section.
(m) Check the Check Connections On Reserve box and click Save.
(n) If you specified Oracle, click the Transactions tab. Check the Set XA Transaction Timeout . In the XA Transaction Timeout field, enter 0. Click Save.
(o) Click Activate Changes.
5. Restart WebLogic Server.
Start the weblogic server for the provision , Endeca Server and Endeca Studio domains independently from command window once it is completed you can check the status of provisioning service by entering below url in browser
Note : We installed non-SSL provisioning service which defaults below parameters in plan.xml so no need to change anything in this file
To configure non-secure communication, in plan.xml:($MW_HOME\domains\end_provisioning\eidProvisioningConfig\plan.xml)
• Change the value of the endeca-server-security-enabled variable to false.
• Change the value of the transport-guarantee variable to NONE.
• Change the value of the protected-url-pattern variable to /DISABLED.
Also, confirm that the value of the endeca-server-ws-port variable is 7001 (the non-secure http port); the
value of this parameter defaults to 7002, which is the secure http port.
Now login to Endeca Studio-->Admin-->My Account -->Provisioning Service enter details in below format and click on SAVE if you message like "Unable to connect to the Endeca Server configured with the Provisioning Service" then some issue with Plan.xml file which is not communicating properly to Endeca server.
{
"port": "provision_port",
"server": "hostname"
}
Now by clicking on New Application in Studio provide "Application name" and select a Data Source as Upload a file --> Excel
once the sheet gets upload click on Next which takes you to Attributes section where you can edit the column names and Data Type/Format of the values as shown below.
You can even Exclude or Include the columns by clicking on Check mark under Include section.
Once it is done the application creation takes time and it shows some text "You can wait for the application creation to be completed, or return to the home page. The application will be available on the home page as soon as it is complete" this is where Endeca creates pre-populated report layouts (best visualizations for our data) and loading data to MDEX engine.
You can see charts and some other components created by default for the SampelData Data set by adding other pages/customize the existing reports.
Reference : http://docs.oracle.com/cd/E40519_01/index.htm
This comment has been removed by the author.
ReplyDelete