Publish Mimics to Operations Hub directly from CIMPLICITY

You can publish a Mimic to Operations Hub directly from CIMPLICITY. This eliminates the two-step process of publishing a Mimic by exporting a screen as a Mimic zip file from the CIMPLICITY server and then importing the Mimic zip file to Operations Hub. Publishing a Mimic to Operations Hub directly from CIMPLICITY is especially useful when you want to publish multiple CimEdit screens simultaneously. You can configure Operations Hub at the project level and globally to avoid configuring it while publishing Mimics. This task describes how to configure Operations Hub at the project level. (Previously, to configure Operations Hub, we selected Operations Hub Configuration in the OPC UA Server tab in the Project Properties window. This has now been updated as mentioned in the procedure below. )

About this task

To configure Operations Hub at the project level:

Procedure

  1. In the CIMPLICITY Workbench window, select Project, and then select Properties.??
  2. In the Project Properties window, select the Operations Hub tab and enter the following details:
    • Server Name: The machine name on which Operations Hub is running or the URL of the Operations Hub Server
    • Port: The port on which Operations Hub is running
    • User Name: The Operations Hub user name used to publish the Mimic
    • Require Trusted Connection: Select this check box to use a trusted connection to publish Mimics. You can also select View Certificate to view the certificate used for the connection.
  3. Select OK.

To configure Operations Hub globally,

  1. Close the CIMPLICITY Workbench window (if it is open), and launch CimEdit from the Start menu.
  2. In the CimEdit window, select , and then select Global Configuration.
  3. In the Global Configuration window, select the Operations Hub tab and enter the following details:
    • Server Name: The server name on which Operations Hub is running
    • Port: The port on which Operations Hub is running
    • User Name: The Operations Hub user name used to publish the Mimic
  4. Select Apply, and then select OK.
    Operations Hub is now configured for Mimics to be published in it. You can publish a Mimic from the following applications: Workbench , CimEdit.
  5. To publish Mimics to Operations Hub directly from Workbench, In the CIMPLICITY Workbench window, select the Mimics that you want to publish to Operations Hub, right-click the Mimics, and then select Publish to Operations Hub.
    Note: In the Publish window, the Server Name, Port, and User Name are automatically populated if Operations Hub has already been configured at the project level. If the fields are blank, enter the details before proceeding to the next step.
  6. In the Publish window, enter the following details:
    • Save To: The location where the Mimics will be saved by default. This field is disabled.
    • Publish to Operations Hub: Select this check box to publish the Mimics to Operations Hub.
    • Overwrite: Select this check box to overwrite Mimics with the same name.
    • Password: The password to publish the Mimics.
    • Require Trusted Connection: Select this check box to publish Mimics only when a trusted connection is used. You can also select View Certificate to view the certificate used for the connection.
    Note: These details are saved after you publish the Mimics. You only need to enter the password if you close and reopen the CIMPLICITY Workbench window.
  7. Select Publish.
    The selected Mimics are published to Operations Hub and appear in the Mimic Management workspace.
  8. To publish a Mimic to Operations Hub directly from CimEdit, go to the location where the Mimic file you want to publish is saved, right-click the file, and select Edit.
    Note: You can publish only one Mimic at a time to Operations Hub from CimEdit.
  9. In the CimEdit window, select , and then select Publish to Operations Hub.
    Note: In the Publish window, the Server Name, Port, and User Name are automatically populated if Operations Hub has already been configured (depending on the project context) at the project level or globally. If the fields are empty, enter the details as described in step 2 of the Configure Operations Hub section before proceeding to the next step.
  10. In the Publish window, enter the following details:
    Note: If you want to save the Mimic to a shared location on a remote server, the network drive should be mapped to the shared location.
    • Save To: The location where the Mimic will be saved locally. You can choose this location since you are publishing only one Mimic at a time.
    • Publish to Operations Hub: Select this check box to publish the Mimic to Operations Hub.
    • Overwrite: Select this check box to overwrite any Mimic with the same name.
    • Password: The password to publish the Mimic.
    • Require Trusted Connection: Select this check box to publish Mimics only when a trusted connection is used. You can also select View Certificate to view the certificate used for the connection.
    Note: These details are saved after you publish the Mimic. You only need to enter the password if you close and reopen the CimEdit window
  11. Select Publish.
    The Mimic is published to Operations Hub and appears in the Mimic Management workspace.