Java API for OLAP (In-Memory DB)
In addition to the HTTP API in the Jedox OLAP server itself, you can also connect to OLAP by using a Java library and the Java API it provides. The library (palojlib) is included in the Jedox installation, and is also available as part of the Jedox SDK. The Java API provides all functions necessary for establishing a connection to the In-Memory DB, retrieving data, and creating or modifying database contents.
An overview and documentation of all functions provided in the Jedox Java API can be found in the PHP Palo API Documentation, which is available online or as a download.
Integrator Scripting API
In Jedox Integrator, the use of scripting languages is foreseen in the following components:
- Groovy functions and jobs
- JavaScript functions and jobs
- Variable definition (Groovy only)
Besides the functionality of the scripting language, Jedox Integrator provides several classes with additional functionality related to Jedox Integrator processing. The methods of the different classes are listed below. Examples for the use of script functions and jobs can be found in the sample Jedox Integrator projects sampleGroovyOlap.xml, sampleGroovyFunction.xml, sampleGroovyJob.xml, and ETLTasks.xml (located in <InstallpathJedoxSuite\tomcat\webapps\etlserver\data\samples>).
Accessing the SOAP API of Jedox Integrator from PHP
Jedox Planning for Salesforce (FR)
Budgétisation, simulation et définition des objectifs dans Salesforce Lightning.
Vous souhaitez accélérer vos processus budgétaires et vos suivis d’objectifs dans Salesforce et passer moins de temps à analyser et modéliser vos données ? L’application Jedox Planning pour Salesforce permet d’accélérer les cycles budgétaires grâce aux moteurs multi-dimensionnels Jedox adaptés à Salesforce Lightening : planification multi-dimensionnelle au niveau détaillé ou agrégé, workflow d’information ou d’approbation, accélérateur de saisie…
L’application Jedox Planning permet de définir et d’ajuster les objectifs commerciaux directement depuis Salesforce, et de suivre les performances réelles par rapport au budget. Pour aller encore plus loin, il est possible de se connecter à d’autres sources de données type ERP et avoir accès aux informations dans Salesforce. Vous pouvez, par exemple, définir et adapter vos objectifs, comparer le réel, le budget et le prévisionnel, ou encore mettre à jour vos prévisions en temps réel.
Avec cette application, les équipes commerciales et finance peuvent collaborer avec les autres départements de l’entreprise pour plus de transparence et un meilleur alignement grâce à un référentiel de données unique.
Dynamisez les performances commerciales d’une équipe de ventes
Les directeurs commerciaux ont deux priorités : faire en sorte que leurs commerciaux concrétisent les objectifs de l’entreprise et mesurer les résultats de manière claire grâce à une vue à 360° du pipeline de ventes. Force est de constater qu’aujourd’hui, les entreprises souffrent d’un manque de visibilité sur leur activité. Or avoir de la visibilité, que ce soit sur le passé, le présent et le futur, est clé dans la mesure où aujourd’hui, la seule constance est le changement, et il faut donc s’adapter en permanence.
Le marché se transforme, votre équipe évolue, vous avez sans cesse besoin de vous situer par rapport à votre plan commercial pour anticiper les changements, adapter votre organisation, et faire évoluer vos plans.
Et si vous intégriez des fonctionnalités de planification et de mesure de la performance à votre CRM Salesforce ?
L’application Jedox Planning pour Salesforce vient pallier au manque de visibilité et de collaboration en imbriquant les fonctions de simulation et de planification budgétaire dans le suivi commercial opérationnel, le tout directement dans Salesforce. Affranchissez-vous des fichiers Excel et travaillez sur des données précises toujours à jour. Comparez l’avancement de vos opportunités et votre prévisionnel à votre plan commercial, et simulez les ajustements organisationnels.
Jedox Planning for Salesforce (EN)
Smart Budgeting, Forecasting and Quota-Setting in Salesforce Lightning
Jedox + Salesforce = Seamless Sales Planning
Speed-up Budgeting, Forecasting and Quota Setting in Salesforce
Jedox Planning for Salesforce, the app for smart budgeting, forecasting and quota setting is available on AppExchange. The powerful app enables customers to accelerate top-down and bottom-up budgeting thanks to the multi-dimensional Jedox planning engine optimized for Salesforce Lightning:
- Multi-dimensional planning on any level or hierarchy
- Multi-step approval workflow
- Copy values from previous period, percentage increase, splashing and more
Align Sales, finance and the rest of the business with integrated planning
Sales managers align budgets and forecasts with finance and other lines of business increasing transparency and integrating plans across the organization:
- Common data foundation
- Integrate the sales plan with financial and operational plans
- Optimized for use with Excel
- Connect additional data sources e.g. ERP etc.
Set quotas and track sales performance. Stay on top of key account revenue and other deals
Jedox Planning for Salesforce makes it easy to set and adjust quotas for sales reps directly in Salesforce and track actual performance against plan:
- Set & edit quotas
- Compare actual, plan & forecast
- Update forecast with latest data
- Analyze gap to target
Tableau Server Connection
Jedox Integrator currently supports connections to Tableau 10.5 and later. The connector can be used with the Tableau REST API. Tableau .tde files are no longer supported; the connector only supports .hyper files.
For this connection a Tableau Connector License is required.
Notes:
- To use this component, the Visual C++ Redistributable Packages for Visual Studio 2013 has to be installed on the system where Jedox is running. Tableau SDK and Tableau Extract API must be downloaded and unzipped, and the respective file path of the bin folders must be added to the system “path” variable. Please refer to Tableau’s documentation.
- Existing TDE file connections will be automatically migrated to TableauHyperFile connections, but the file extension must be manually changed from *.tde to *.hyper.
- Logs can be read by adding environment variables TAB_SDK_LOGDIR and TAB_SDK_TMPDIR to the desired paths, if desired.
How to Connect Jedox and Tableau (TDE File)
Jedox PowerBI Connection
This component defines a connection to Microsoft’s Power BI, a business analytics service. This connection is then used in a PowerBI Load to load the data from Jedox into Power BI, where it can be used for analysis and visualization.
To use Power BI, you must have an active subscription to Office 365 with Power BI and a Power BI license from Jedox.
The connection requires two steps:
- Creating an app in Azure Active Directory that enables Jedox to communicate securely with Power BI
- Creating an PowerBI connection in Jedox Integrator
Note: the Power BI API has some limitations, including an hourly limit of 1,000,000 rows per dataset. Please refer to Microsoft’s documentation on Power BI REST API Limitations for details.
1. Setting up the Azure Active Directory app
To connect to a Power BI instance from Jedox, you must first create an application (app) in Azure Active Directory (Azure AD). This can be done from one of the following Microsoft links:
When you set up the app, you should apply the following settings:
- The application type must be native/client-native.
- Set the sign-on URL to http://localhost (this sign-on URL is not used with native apps).
- Select “Power BI Service” as the API. If this option is not on the list, then you probably don’t have a license for it.
- For permissions, select all delegated permissions except those that require admin consent.
- Copy the Application ID (Client ID) for use in the next step, setting up the PowerBI connection in Jedox Integrator.
For details, please refer to Microsoft Azure App Services Documentation.
2. Setting up the PowerBI connection in Jedox Integrator
Main Settings
| Azure Application ID: | The application ID in Azure Active Directory (also called App ID or Client ID), as established in step 1 above. |
| Group Name: | Name of the Power BI group. The group’s workspace will be the target of Power BI loads. If no group is specified, the default workspace of the user is used. |
| User Name: | Power BI user name (Microsoft Office 365 user name) |
| Password: | Power BI user password |
Advanced Settings
Verify: the
certificate is verified.
Trust: the certificate is imported to the keystore if not yet available.
Off: no SSL used.
What is the TM1 REST API
The TM1 REST API is a relatively unexplored method of interacting with TM1 and allow external applications access to server objects directly. Introduced in version 10.2 and constantly being improved upon with each Planning Analytics release, the TM1 REST API conforms to the OData V4 standard. This means that the REST API returns standard JSON objects which can be easily manipulated in most programming languages. This is a change from previous proprietary TM1 APIs (such as the VBA /Excel and Java APIs) that required handling of custom TM1 objects.
Currently almost all administrative aspects of the TM1 server, which are available in Architect and even some that are not, such as retrieving thread status and canceling threads (functionality provided by TM1Top) can be handled using the REST API. Functions and actions are available to create cubes, dimensions, subsets, hierarchies, TI processes and rules as well as monitor transaction logging and even commit TI code to a GIT repository.
How do I Enable the REST API?
First you have to ensure that your TM1 version supports the REST API. It was introduced in version 10.2, however a number of key features are not available before 10.2.2 FP5, so that is the recommended minimum version.
To be able to access an instance via the REST API, the tm1s.cfg file parameter “HTTPPortNumber” must be set to a unique port. The instance may need to be recycled prior to use as this is a static parameter.
What Can’t I Do with the REST API?
At its core, the TM1 REST API is not end-user ready. It is merely a tool for developers to interact with TM1 from external applications/languages and more easily integrate TM1 into your data stream.
It is possible to create end-user consumables (such as dashboards and reports that are referencing / interacting with data stored in TM1 cubes) using the REST API as the connection to TM1, however it should be noted that these solutions will have to be custom-built in another language (such as HTML, PHP, Python, Java, Powershell or a combination of some languages) or built on top of PAW (which in the back-end uses the REST API to connect to TM1).
How is the REST API being used in the real world currently?
The REST API is the back-end connection for both IBM Planning Analytics Workspace (PAW) and IBM Planning Analytics for Excel (PAX). Any reports/dashboards built in these tools will use the REST API seamlessly by default with no additional configuration/development required.
A majority of the current use case of the REST API in Production-level deployments at a number of clients is to remotely execute TI processes in a multi-threaded fashion. There is a benefit in using the REST API to kick off parallel TI processes over the old TM1RunTI.exe utility in that the REST API will avoid CAM logon lock contention, as well as avoiding the need to build a custom thread tracking mechanism. When coupled with the “async” library within Python, the Python script is able to manage thread limits and overall execution status tracking without the need for building flag files into your TI’s.
In addition to using the REST API to kick off TI processes, there are other clients which are using it for minor data sync’s between instances. For instance, two different TM1 instances which have copies of the same exact cube structure. Rather than using flat files and custom TI processes to push data between instances, a simple Python script to create and push a cellset from source instance to target instance accomplishes the task without the need for a third-party software to execute the processes on both instances in sequence.
https://ibm.github.io/paxapi/#macro-files
à Paris par 