Creating a package

From the Build menu, select Create Package to package all project elements (including permission scripts, extraction scripts, schema, documentation, and so on.) into an installable package that can be deployed on an Infor Risk & Compliance server. Alternatively, click Build Package to build a package. Before you create a package, you will be prompted to perform the Project Integrity Test. Click Perform Integrity Test. If errors are encountered in the Integrity test, you will have to fix all the errors before you can create a package. However, you can go ahead with creating the package if only warnings are found during the integrity test.

Note: To create Permission Script for Custom Insights, you need to create a user with appropriate rights, based on the ERP security, to extract data.

Depending on the ERP project to the packaged, the Create Package window contains the following panels:

SAP or Lawson Projects

  1. If you are packaging a SAP or Lawson project, provide information on the following panels:
    • Build Details: This panel contains an automatically generated build number. The build number is incremented by 1 every time you build a project and generate it.
    • Output Information: In the Output Information field, provide the path where the package should be created. You can either browse for a folder or create a new folder.
  2. After providing the required details, click Create Package. The Build Log tab displays the progress of the packaging. Once the package is created, the last entry on the log will display Package generation completed successfully.
  3. Click Close.
  4. Go to the path you specified for package creation. You will see a folder with the build number. The INSIGHT folder contains the Insight folder and InsightInstaller.exe. The Insight folder contains the objects selected for packaging.

Oracle, PeopleSoft or Infor Projects

  1. If you are packaging an Oracle or PeopleSoft project, provide information on the following panels:
    • Build Details: This panel contains an automatically generated build number. The build number is incremented by 1 every time you build a project and generate it.
    • Package Contents: This panel contains:
      • Modules for Offline extraction scripts: The modules displayed depend on the modules you are licensed to use.  For example. if you select only GL, then only GL objects will be extracted when using offline extraction sripts. Online scripts are generated for all licensed modules.
      • Category for Offline Extraction Scripts: Selecting a category ensures that only objects of that category are extracted when using offline extraction scripts. Online extraction scripts will contain all objects. Note that a separate script is generated for each category. If all 3 categories are selected, 3 scripts will be generated.
      • Databases for Extraction Scripts: These settings apply only to PeopleSoft or custom projects with multiple backends. Settings apply to both online and offline extarction.
      • Output Information - In the Output Information field, provide the path where the package should be created. You can either browse for a folder or create a new folder.
  2. After providing the required details, click Create Package. The Build Log tab displays the progress of the packaging. Once the package is created, the last entry on the log will display Package generation completed successfully. You can package multiple Insights.
  3. Click Close.
  4. Go to the path you specified for package creation. You will see a folder with the installed build number. The INSIGHT folder contains the Insight folder and InsightInstaller.exe. The Insight folder contains the objects selected for packaging.
    Note: For Oracle and PeopleSoft projects, Studio generates offline extraction scripts and permission scripts in a separate folder available within the package folder. Online extraction scripts reside within the Settings folder.
    Note: When extracting data using offline extraction scripts, the output will be in a CSV format.

    For Custom Insights, create a user with appropriate rights, based on the ERP security, to extract data.