This post is part of a series of posts on implementing Jet Reports and is part of the Jet Enterprise sub-series.
The final step in automating the deploy and execution of the project, is to create the scehdule. Do this in the Jet Data Manager Server by selecting the Execution tab, right click on the execution package to which you want to add the schedule and then click Add Schedule:
Continue reading “Implementing Jet Enterprise: Schedule Execution Package”
This post is part of a series of posts on implementing Jet Reports and is part of the Jet Enterprise sub-series.
In the last post, I stepped through the creation of an execution package; I am going to set this to execute automatically on a schedule, but first I am going to manually run it to ensure that it works.
To test the execution package, select the Execution tab, right click on the execution package to test and click Execute:
Continue reading “Implementing Jet Enterprise: Test Execution Package”
This post is part of a series of posts on implementing Jet Reports and is part of the Jet Enterprise sub-series.
To automatically update the Jet Enterprise cubes, we need to create an execution package.
To do this, select the Execution tab, right click on the Execution {Package node and click Add Execution Package:
Continue reading “Implementing Jet Enterprise: Create Execution Package”
This post is part of a series of posts on implementing Jet Reports and is part of the Jet Enterprise sub-series.
Jet Enterprise cubes can be automatically updated using an execution package. A notification can be created for the execution package so that admins can be notified of any issues during the execution.
In this post, I’m going to create a notification and in the next post will cover the creation of the execution package itself.
To create the notification, select the Execution tab, right click the Notifications node and click Add Notification:
Continue reading “Implementing Jet Enterprise: Create Event Log Notification for Execution Packages”
This post is part of a series of posts on implementing Jet Reports and is part of the Jet Enterprise sub-series.
Over the last few posts, I have shown the installation and deployment of Jet Enterprise and have manually updated the data warehouse and OLAP cubes. We have then tested the cubes in Microsoft Excel to confirm the cubes are populated and working correctly.
However, a BI solution needs to automatically update so that new data is included without the user needing to take any action other than refreshing the report. There is a few steps which need to be followed to do this; over the next few posts in this series I’m going to show how Jet Enterprise can be configured to do this.
This post is part of a series of posts on implementing Jet Reports and is part of the Jet Enterprise sub-series.
With the basic Jet Enterprise installation and configuration now complete, Microsoft Excel can be connected to the cubes to test that everything is working as it should; launch Microsoft Excel, select the Jet tab and click the Data Source Settings button:
Continue reading “Implementing Jet Enterprise: Connect Microsoft Excel to the Jet Enterprise Cubes”
This post is part of a series of posts on implementing Jet Reports and is part of the Jet Enterprise sub-series.
In the last post, I showed how to deploy and execute the project; in this post, I am going to deploy and execute the OLAP Cubes which will make them available for reporting. For a detailed description of the deploy and execute process, see the Jet Support article. The deploy and execute can be done separately, but for the first deploy and execute during implementation, I’d tend to do them together.
In this stage we want to deploy and execute the entire OLAP Cubes. To do this, click on the Cubes tab, then right-click on the OLAP Servers top level node and click Deploy and Execute:
Continue reading “Implementing Jet Enterprise: Deploy and Execute OLAP Cubes”
This post is part of a series of posts on implementing Jet Reports and is part of the Jet Enterprise sub-series.
Over the last few posts, I’ve been stepping through the basic installation and configuration of Jet Enterprise; in the last post, I covered the configuration in Connection Manager which connects Jet Enterprise to the installation of Microsoft Dynamics GP. In this post, I’m going to cover the first deploy and execute of the project; the short description of deploy and execute is that the data structures are created (deploy) and populated (execute).
For a detailed description of the deploy and execute process, see the Jet Support article. The deploy and execute can be done separately, but for the first deploy and execute during implementation, I’d tend to do them together.
In this stage we want to deploy and execute the entire project. Do this by right-clicking on the project name at the top of the navigation pane in the Detail tab and click Deploy and Execute:
Continue reading “Implementing Jet Enterprise: Deploy and Execute the Project”
This post is part of a series of posts on Jet Reports.
In the last post, I covered the creation of the project; in this post, I’m going to cover the configuration of the project in the Connection Manager which tells the project which Microsoft Dynamics GP system it is to run against:
Continue reading “Implementing Jet Enterprise: Connection Manager”
This post is part of a series of posts on Jet Reports.
In the last post, I covered the creation of the Jet Enterprise project repository; in this post, I’m going to go through creating the project.
To create the project, launch the Jet Data Manager Server and, from the File menu, select CubeStore:
Continue reading “Implementing Jet Enterprise: Create Project”