Jedox 3rd Party Access/MDX: Needed address changes

image_pdfimage_print

There are three possible installation scenarios:

  1. Jedox Client, Jedox Server, and Jedox ODBO Provider on the same machine (all-in-one installation)
  2. Jedox Client + Jedox ODBO Provider on Machine 1, and Jedox Server on Machine 2
  3. Jedox Client + Jedox ODBO Provider on Machine 1, and Jedox ODBO Provider + Jedox Server on Machine 2

The configuration file for the Jedox ODBO Provider is stored in the Jedox folder (…\Jedox Suite\odbo\ config.ini) and contains four relevant items: the PaloAddress, MDXAddress, PaloPort, and MDXPort:

PaloAddress The IP address the Provider expects to find a Jedox Server.
MDXAddress The IP address the Provider is bound to. This item is especially relevant in the case of a multi-IP machine. The IP used here will be the IP the clients use to connect to the Provider. 
PaloPort The port used to connect to the Jedox Server. 
MDXPort The port the clients use to connect to the Provider.

The other relevant configuration file is palo.ini, located in the Jedox folder at  …\Jedox Suite\olap\data. Only one single entry is relevant to the scope of the current article: the http entry (highlighted in the screenshot below) represents both the IP the Jedox Server is bound to and the port used by the Jedox Server. 

Scenario 1: all-in-one installation

This is the default installation. Both the Jedox Server and the Jedox ODBO Provider are on the same machine. Connections to the data are executed from the same machine. For this installation, there is no need to change the .ini files.

Scenario 2: Jedox Server on Machine 2

In this configuration the Jedox Server is on a remote machine. The machine that connects to the data has the Jedox ODBO Provider locally:

In this case, both the Jedox Server and the Jedox ODBO Provider require configuration:

Jedox Server: edit the Palo.ini file and look for a construct like http “localhost 7777”. Change localhost to the IP of Machine 2. 
For example: http 80.72.130.210 7777

Jedox ODBO Provider: edit the config.ini file and look for a construct like “PaloAddress  127.0.0.1”. Change 127.0.0.1 to the IP of Machine 2.
For example: PaloAddress 80.72.130.210

Restart both the local machine and the Server to commit the changes. Alternatively, you can restart only the relevant services: JedoxSuiteMolapService and JedoxSuiteMDXInterpreter.

Scenario 3: Jedox Server and Jedox ODBO Provider on Machine 2

Here the Jedox Server and the Jedox ODBO Provider are on the remote machine. However, in order to access the data, the machine used for the client must have a second copy of the Jedox ODBO Provider installed:

In this case, the Provider will be split between a thin client interface on the client machine and the main provider working on the server machine. The Jedox Client gets the IP address of Machine 2 while connecting with the Jedox Server. Therefore, only the Jedox ODBO Provider on Machine 2 needs the following changes in the config.ini:

Jedox ODBO Provider: edit the config.ini file and look for a construct like “MDXAddress  127.0.0.1”. Change 127.0.0.1 to the IP of the Machine 2. 
For example: MDXAddress  80.72.130.210

Restart “JedoxSuiteMDXInterpreter” under Start → Control Panel → Administrative Tools → Services or restart Machine 2 to commit these changes.

image_pdfimage_print
Was this post helpful?
NoYes (No Ratings Yet)
Loading...