Configuration Portability
Configuration Portability enables you to copy selected configuration settings from one system to another system using a simple export and import mechanism.
Last updated
Configuration Portability enables you to copy selected configuration settings from one system to another system using a simple export and import mechanism.
Last updated
Configuration Portability enables you to:
Select the configuration settings you want to copy
Export the settings from the source system
Import them into the target system.
Further, you will also understand exactly:
How long each import will take
What manual changes you will still need to make (CMDB, Services, Service Actions, etc)
Configuration Portability, as a feature of ASM, allows you to move work packages from one system to another. Configuration Porting is not bi-directional. There can only ever be 1 source system.
While the process itself is actually simple, the underlying actions are complex and you may end up porting items you did not intend to port. For this reason, please review this section, and the following pages carefully to ensure you understand how Configuration Porting works before undertaking this task. It would be wise to see the assistance of Alemba for your first time. If you need to request support for these features, please contact Alemba Support
If you are a Cloud Customer, Config Port files can be created from your system, but the import must be done on the server. You will need Alemba Support to assist with this activity.
Create your export files and label them so that Support will know what order to bring them in. For example:
[Your Change#]-[File 1]-System Settings
[Your Change#]-[File 2]- Screens
[Your Change#]-[File 3]-Message Types
[Your Change#]-[File 4] - SSP Settings
An alternative to Configuration portability exists, please see:
Organizations often set up test systems when they implement major changes to an existing production system. The test system is analyzed to ensure that all changes have been applied correctly before updating the production environment. It is imperative for organizations to follow this procedure in order to reduce the likelihood of errors or failures when these changes are implemented on the production system.
ASM Systems are business-critical and require complex configuration and setup by administrators. As a result, it is typical to set up a test system for ASM Core, ensure the setup reflects the organization’s requirements, make changes if required, and then recreate the settings and data from the test system into the production system. Depending on the scale of an organization’s operations, this task can be time-consuming.
Configuration Portability enables you to copy selected configuration settings from one system to another system using a simple export and import mechanism. For on-premise customers, all this can be performed directly from the client application, which means that you do not need to have access to the ASM Core server to import and export configuration settings.
For example, if your organization has 3 environments then:
Once an organization has developed screens and configured settings on a development system (referred to as the source), the changes are imported and validated in the test system (referred to as the target ), and then the same source files are imported into the production system (referred to as the master target ).
For example, if your organization has 2 environments then:
Once an organization has developed screens and configured settings on a Test system (referred to as the source), the changes are exported as source files. The source files are imported into the production system (referred to as the master target ).
You can transfer Configurations - These are the administration settings pertaining to functional areas such as Service Desk, Workflow Management, Configuration Management and Service Level Management. The following data can be ported:
System Administration settings
Screens, forms, and message templates configured in ASM Designer
Data cannot be ported:
Call and Request Data
Person Records/Details
CMDB Items
AI Ops Rules
System default values (such as the default System Title defined in System Administration)
Templates (such as Workflow Templates and Call Templates) You must use the Workflow Port Utility
IPK Workflow Rules
CMDB Items and Services, Service Actions
Forum Management Rules
Activity Logs
SLM Agreements
Person records
Passwords and Email settings
System customizations, stored procedures, and integration settings. (These settings involve files which are not located within the database, such as SQL files, or HTML files.) They must be transferred manually between the sourc