Month: May 2018

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”

This post is part of a series of posts on Jet Reports.

The installation of Jet Enterprise leads into the creation of the project repository, which I’m going to cover in this post.

There are a few fields which need to be completed for the project repository to be created.

First, enter the full instance name of the SQL Server which will host the repository database.

Second, either accept or change the Database and click the Create button (I added the Jet prefix to the database name).

Third, enter the full instance name of the SSIS server name.

Fourth, select the authentication method; I’ve selected Windows authentication as the user I am logged in as, is a SQL Server sysadmin.

Click OK to proceed:

The next step is to create the project, which I will cover in the next post.

This post is part of a series of posts on Jet Reports.

So far in this series, I’ve covered the installation and configuration of Jet Express and Jet Professional; these are the bottom and middle tier of Jet Reports.

The Express version is the most basic one and only has a, very simple, client installation process; the Professional version is a little more complex and has an optional server component.

Jet Enterprise is a much more complicated installation and configuration than either of the lower tier versions. That said, while being more complicated than the others, it is still a fairly simple process.

With Jet Enterprise, the server components are mandatory and are where the data warehouse and cubes are built and deployed. I will be covering all of this over the coming posts, but the first item to cover is the installation. To install the software, the first thing you need to do is download the software from Jet Reports:

Continue reading “Implementing Jet Enterprise: Installation”

This post is part of a series of posts on Jet Reports.

The next set of posts is about the top tier of Jet Reports; Jet Enterprise. Jet Enterprise includes the complete reporting functionality of Jet Professional, so the prerequisites of Jet Professional also need to be met.

The prerequisites for Jet Enterprise are outlined below.

• Hardware
  • Hardware requirements are going to vary based several factors, such as number of users, size of databases, rate of growth, data refresh timings as well as if the server is dedicated to jet Reports or if it is shared with other applications.
    Jet Reports have a support topic covering their Server Hardware Sizing Recommendations.
• Operating System
  • Microsoft Windows Server 2016
  • Microsoft Windows Server 2012 and 2012 R2
  • Microsoft Windows Server 2008 SP2
• Prerequisites
  • Microsoft .Net Framework 4.5, including ‘ADOMD.NET for SQL Server 2005’ (which can be downloaded from Microsoft)
• Microsoft Office
  • Microsoft Office 365 (2013-2016 Desktop Edition Only)
  • Microsoft Office 2010 – 2016