Publishing my project to the Infor Risk & Compliance server

Publishing the Insight to the Infor Risk & Compliance server as follows:

  1. From the menu bar, click Build and then Publish. Before you publish your changes to the Infor Risk & Compliance server, you will be prompted to perform the Project Integrity Test and verify the Infor Risk & Compliance connection that you created.

    Ensure that the Studio user publishing the project has Administrator rights on the Infor Risk & Compliance server.

  2. Click Perform Integrity Test. If errors are encountered in the Integrity test, you will have to fix all the errors before you can publish your changes. However, you can go ahead with publishing if only warnings are found during the integrity test.
  3. From the Database Server drop-down list, select the name of the Infor Risk & Compliance server to which the changes are to be published.
  4. Click Test Database Connection. A successful test is indicated by an icon. You will now be prompted to provide the credentials for the user accessing the Infor Risk & Compliance application server.
  5. Provide the name of the application server, the domain and the credentials needed to access it.
  6. Click Test Application Server Connection. Studio will display a message stating that Studio is ready to test. If an Insight is already deployed on the Infor Risk & Compliance server, the Target Server Platform Version  and Target Server Insight Version fields are automatically populated.  If no Insight is deployed, the fields will display the message that the Insight is not installed.
  7. Select the modules to be published. Objects pertaining to these modules will be created.
  8. To run a test and an impact analysis before the actual publishing, select the Run in Test Mode and the Perform Impact and Change Analysis check box. When you select the Run in Test Mode check box, test mode simulates publishing and enables you to verify that details such as user permissions are correct. You will also be informed of any errors before changes are made to the database. Once the test is complete, information on the Progress Log (which informs you of the tables that Studio is writing into) and Action Log (what is written into the table) tabs enable you to verify whether your changes are ready to be published to the Infor Risk & Compliance server. When you select the Perform Impact and Change Analysis check box, the project will be analyzed against the Infor Risk & Compliance server on which the project is to be published. On completion of Impact Analysis, a report is generated. You can review the report and decide whether or not to publish the project.
  9. Once you are satisfied that the test is successful, clear the Run in Test Mode check box and click Publish. Studio publishes the new Insight version to the Infor Risk & Compliance server. In case a project with an existing GUID is published, the existing Insight version will be overwritten, including all files, registries and database components. You can publish multiple insights. Data will be retained in tables if the schemas of both projects remain unchanged or if tables are added to the new project. However, if the new project deletes a destination table that was present in the old project, the table and all its data will be deleted.