Integrate Meridian Enterprise with Meridian Portal

Before you can configure the Meridian Portal integration, you must first purchase a paid subscription for Meridian Cloud. There are three subscription levels: Meridian Cloud Project, Meridian Cloud Business, and Meridian Cloud for Life Sciences.

After you have purchased a paid subscription, your Accruent representative will create a Meridian Cloud tenancy for you. Your tenancy is your specific instance of Meridian Cloud. Your Accruent representative will provide you with the information you need to configure your tenancy's integration with Meridian Enterprise.

Additionally, you must also have a Meridian Enterprise license for the Advanced Project Workflow Module. This module is not part of the base licenses for Meridian Enterprise.

Contact your Accruent representative if you are interested in purchasing a Meridian Cloud subscription, or if you need to purchase an additional license for the Advanced Project Workflow Module.

Additionally, you must meet the following technical requirements:

1. You must be using a currently supported version of Meridian Enterprise.

2. You must implement TLS 1.2.

For each vault that will be connected with Meridian Portal, you must configure the following properties in the Administrator.

In the Configurator, create at least one folder type with the Can be linked to Meridian Portal projects setting enabled. After creating a folder type with this setting enabled, the ProjectFolderPropertySet property set is created automatically.

Once you have created your folder type, create a project definition that uses this folder type.

Ensure that the Link to Meridian Portal and Send to Portal commands are enabled for the appropriate scopes. You can find these commands on the Command Filter tab.

You must perform the following tasks related to repositories:

1. Create an Explorer repository. The repository name must differ from your Meridian tenancy name, otherwise, the Validate Synchronization task fails with the The selected job is not valid for this operation error.

   Only documents synchronized to this repository will be available in Portal.

2. Configure the repository.

3. Set the following values in the Vault Overview Options in the Administration Console:

   • Document number property – Set this value to any custom property

   • Project number property – Set this value to ProjectFolderPropertySet.ProjectNumber

     Important!

     If there are multiple vaults registered in Enterprise Server, your vaults must be configured to ensure that the values of ProjectFolderPropertySet.ProjectNumber are unique across all your vaults.

     How project numbers are calculated depends on your configuration. Usually a VBscript function is used to calculate them.

     A simple way to keep project numbers unique is to give them a vault-specific prefix. For example, if you have a vault for Unit 1, Unit 2, and Unit 3, then the script used for Unit 1 can use U1- as a prefix.

     If this is not feasible, you can also use a central SQL database and use SQL queries to generate unique numbers.

     Another approach is to generate sequence numbers using Vault.Sequence (“MySeq”).Next in one of the vaults and use Vault.CallRemote in the other vaults to access this sequence.

Next, you must create a repository synchronization job. A synchronization job reads data from the Meridian Enterprise source vault and exports it to one or more intermediate data (not document content) files.

To create a repository synchronization job:

1. Create a Publishing Job.

2. Configure the Publishing Job.

3. Configure the Synchronization Options.

A Package Export job is a publishing job which defines a destination for exporting packages. There should be only one Package Export job per Explorer repository.

To create a package export job:

1. Create a Publishing Job.

   • In step 3 of the Create a Publishing Job procedures, select Package Export as the job type.

   • In step 10 of the Create a Publishing Job procedures, select Meridian Portal as the destination system.

2. Configure the Publishing Job.

Next, you will need to create an import profile. The settings in the table below are specific to the integration.

You can modify the following VBScript and add it to the Configurator to assign document numbers to new documents submitted in packages by external business partners. By default, the documents are assigned GUID values as temporary document numbers.

Sub ImportPackage_AfterImportedFromPortal()
                        Document.psGeneral_DocumentNr = Document.psGeneral_Discipline & Right ("00000" & Vault.Sequence (Document.psGeneral_Discipline).Next, 5)
                        Document.ApplyPropertyValues 'To save the update
                    End Sub

You can modify the following VBScript and add it to the Configurator to configure the display of the Export Package and Import Package property pages in PowerWeb.

Function ExportPackagesPage_IsVisible()
                        If Not Document Is Nothing Then
                        'Add your code for document objects
                        ExportPackagesPage_IsVisible = True
                        ElseIf Not Folder Is Nothing Then
                        'Add your code for folder objects
                        End If
                        End Function

                        Function ImportPackagesPage_IsVisible()
                        If Not Document Is Nothing Then
                        'Add your code for document objects
                        ImportPackagesPage_IsVisible = True
                        ElseIf Not Folder Is Nothing Then
                        'Add your code for folder objects
                        End If
                    End Function

In the Change Tenancy Settings procedures linked to by the Connect Meridian Cloud tenancy in Administration Console heading above, there are two options related to package scanning.

• Package scanning interval — The interval in minutes to scan for new packages. The default is 5 minutes. This option is only available after a Meridian Portal tenancy has been registered.

• Import scanned packages — If enabled, packages that are successfully scanned are imported automatically and do not need to be imported manually as described in Import an Import Package. This option is intended for use with packages sent from Meridian Portal.

Learn how to configure these settings.

To save temporary package files:

1. Navigate to C:\ProgramData\BlueCieloECM\EnterpriseServices\PublishingCapability.dat.

   Learn more about the settings in this file.

2. Edit the file in a text editor.

3. Set the KeepPackageTempFiles setting to true.

4. Save your changes.

   Your import and export package files can now be viewed in the following folders:

   • C:\ProgramData\BlueCieloECM\EnterpriseServices\Meridian360\import

   • C:\ProgramData\BlueCieloECM\EnterpriseServices\Meridian360\Export