Configuration Migration

Modified on Mon, 03 Feb 2014 at 02:16 AM

Infoborders includes several tool to migrate settings from one environment to another (example from development to production).


Users and Roles

Currently there are no tools for migrating users or roles from one environment to another.


Portals

The portals itself required manual setup (cut and paste from between environments), however there are several configuration settings that can be migrated.


Portal Settings - Configuration

Portal configuration page contains  CustomFields, EditHTML and main.ini configuration 

  • CustomFields, contains information about custom fields defined for a specific portal.  
  • EditHTML, contains code for custom pages such us forms used to create documents on the portal.  
  • main.ini, contains custom configuration properties.  

To migrated these settings from one environment to another create the appropriate entry in the destination environment, if such entry does not exist, and paste the configuration from the source environment.


Stylesheet

Stylesheet are used to define now documents and processes are displayed on users screens in html/pdf/RTF/excel formats.  Stylesheets are based on XML XSLT standard. In order to migrate stylesheet create the appropriate entry in the destination environment and paste the XSLT code from the source environment.


Email Notification Templates

Email notification templates are used when generating email messages that are sent from the system.  Within a given environment the notification templates can be copied into the portal when using portal template.  Between the environments the template definitions may need to be created by hand and edited.  When editing email notification templates the best way to copy the code is by switching the template into a "Show Source" mode and cutting and pasting between environments.


Company

Currently company setups including Company, Company IDs and Relationships needs to be setup by hand.  The system however, will create a Company and Company IDs when a new files is loaded for which there is no confirmation. The administrator will need to edit this information to make it readable.  The default system generated Companies and Company IDs use the sender/receiver ids to generate the names.


Processes Templates

Processes are comprised by functions and shared modules that are organized within a process template.  In order to migrate functions and modules navigate to Export/Import page found under Supper Admin | Processes menu.  On this page select the functions and modules to export on the source environment and press Export button found on the bottom of the page.  On the destination environment navigate to the same page, select the exported file and press Import button. 


The process templates themselves need to be manually created using the UI.


DPS (Data Processing Service)

Configuration related to the DPS service needs to be manually cut and paste between the different environments.  


Scorecard Event Types

Scorecard event types need to be manually setup in each environment.  No former migration options are found.


Community Management

Types

Community management contains organizations and persons which in turn can have properties of different types.  For example a Phone property can have a type of Home, Work, Mobile, etc.  These property types can be configured under Super Admin | Community Management.  Currently these need to be manually setup at the portal level if custom configuration is needed.  Similarly, there is no migration option between environments.


Organizations \ Persons

The Advanced Import/Export page under Community management provides a mechanism to export and import both organizations and persons.  To migrated organizations and person, download in XML format and then load the same file in the destination environment.  Each exported organization and person will have an id, which will be used when loading the file back.


Security

Security includes roles, permissions to Companies, Relationships, access to pages and report.  Currently all configurations need to be made by hand,


Localization

Infoborders contains multi language support for most of its pages.  Location can be migrated from one environment to another.  Synchronize localization resources page can be used to export and information the configuration file. Not that this functionality is currently in beta.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article