Copy main config from data area to data area

 7 Replies
 1 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
blmackey
Basic Member Send Private Message
Posts: 6
Basic Member

I deleted my main config on one of my test databases.

I was deleting some redundant properties when I accidentally clicked the wrong trash can.

Not all is lost, but I'd rather not key everything in again from our development server.

 

Any help you can provide is greatly appreciated.

-Bryant

Terry P
Veteran Member Send Private Message
Posts: 234
Veteran Member
I don't believe it is possible. We had to manually enter everything when we upgraded.
blmackey
Basic Member Send Private Message
Posts: 6
Basic Member
Thanks Terry. I had hoped this wasn't the case.
Good thing I have two monitors!

I won't comment on the user interface that allowed me to do this so easily....

-Bryant
balayogesh
Basic Member Send Private Message
Posts: 11
Basic Member
You can use an export/import process for scenarios such as:

Moving configurations from a development environment to a test environment
Moving configurations from a development environment to a production environment
Exporting/Importing from a Development Environment to a Test Environment
When you export and import configurations between a development environment and a test environment, you can take a less rigorous approach than when you import configurations into a production environment.

In the development environment, run Verify Configurations (cdverify) to ensure that the configurations you want to export are valid in the current environment.
In the development environment, export the configurations you want to later import to the test environment. You can use the Export option within the Configuration Console in the development environment or run the Configuration Data Export utility.
Administration Console > Configuration and Personalization > Configuration > Export Configurations
If you use Configuration Console Actions > Export, copy the export file to the test environment.
Import the file from the development environment. Run Configuration Data Import.
Administration Console > Configuration and Personalization > Import Configurations and Personalizations
Exporting/Importing from a Development Environment to Production Environment
In this scenario, you use a development environment to create configurations (and possibly also personalizations) and then export those to the production environment. You must take care in this process to preserve the existing configurations.

Create a backup of your production configurations. In your production environment, use the Export option in the Configuration Console or use the Configuration Data Export utility.
Administration Console > Configuration and Personalization > Configuration > Export Configurations
If you also want to work with personalizations, create a backup. Use the Configuration Data Export utility.
Administration Console > Configuration and Personalization > Personalization > Export Personalizations
In the development environment, run Verify Configurations (cdverify) to ensure that the configurations you want to export are valid in the current environment.
In the development environment, export the configurations you want to later import to production. Use the Configuration Data Export utility.
Administration Console > Configuration and Personalization > Configuration > Export Configurations
Administration Console > Configuration and Personalization > Configuration > Export Personalizations
Import the file from the development environment. Run Configuration Data Import.
Administration Console > Configuration and Personalization > Import Configurations and Personalizations
balayogesh
Basic Member Send Private Message
Posts: 11
Basic Member
Use this procedure to export configurations from the Configuration Console as opposed to exporting configurations via the export utilities. This method enables you to export all configurations for either the application or the security configuration type or export one or more selected configurations from within the configuration type.

To export all configurations from the Configuration Console

Access the Configuration Console for the type of configurations you want to export (Application or Security).
From the Actions menu, select Export.
Select the Select all Configurations check box.
Click Browse and navigate to the locations where you want to save the zip file containing the exported configurations.
Provide a name for the zip file and click Save.
Click Export.
To export individual configurations from the Configuration Console

Access the Configuration Console for the type of configurations you want to export (Application or Security).
From the Actions menu, select Export.
Make sure that the Select all Configurations check box is cleared.
Expand the tree hierarchy of configurations in the pane and select the configuration to export. You can use Ctrl+Click to select multiple configurations.
Click Browse and navigate to the locations where you want to save the zip file containing the exported configurations.
Provide a name for the zip file and click Save.
Click Export.
balayogesh
Basic Member Send Private Message
Posts: 11
Basic Member
Use this procedure to export configurations. Configurations are created through the Configuration Console in Infor Rich Client. They are various types of modifications that an administrator can make to Infor Rich Client, including look-and-feel changes to menus, pages, and various user interface objects and actions associated with a business class, and including changes and additions to security classes.

You may want to export configurations as a way to make them available in a test system, or you may development configurations on a test or development system and then want to make them available for import to another system.

To export configurations

Navigate to Start > Applications > Administration Console > Configuration and Personalization > Configuration > Export Configurations.
On the Configuration Data Export to FTP form, specify what you want to export:
Subdirectory Name
If you want to export the configuration to a subdirectory of the FTP site directory, specify that directory.
Format Type
Select Directory or Zip File.
Zip File Name
If you are exporting to a zip file, provide the name of the zip file.
Filters
Select the appropriate check boxes to indicate the types of configurations you want to export.
Click OK.
Terry P
Veteran Member Send Private Message
Posts: 234
Veteran Member

I don't think we're talking the same "configuration" here. It is the Process Flow configuration, and the System or Main set that needs changed.

Kyle Jorgensen
Veteran Member Send Private Message
Posts: 122
Veteran Member
We have a bunch of configuration sets, each with a bunch of properties. Being able to copy from one productline to another was a must for us. We worked with Infor to get the instructions on how to do it.

These instructions will copy the configuration sets from one product line to another in Landmark. After they're copied you'll need to edit any values that may need to be different because of the new productline.

[code] Export Data - performed on source landmark system -------------------------------- Navigate to the landmark folder Run `enter` First try this command: dbexport -z _sets.zip -C PfiConfiguration PfiConfigurationProperty Then examine _sets.zip. If it looks good, delete _sets.zip and run these commands: dbexport -z _sets.zip -C PfiConfiguration PfiConfigurationProperty PfiClassicConnection PfiLandmarkConnection PfiM3Connection PfiEventHubConnection PfiFTPConnection PfiFileActivityConnection PfiEmailConnection PfiIONConnection PfiJDBCConnection PfiWebServiceConnection PfiWebRunConnection PfiJMSConnection PfiMQConnection PfiTXConnection PfiSystemCommandConnection PfiCustomConnection PfiCloverleafConnection Next copy _sets.zip to the destination landmark system Import Data - performed on destination landmark system -------------------------------- Navigate to the landmark folder Run `enter` First try this command dbimport -z _sets.zip -C -V Were there any critical errors reported with the above validated import option? No, then run: dbimport -z _sets.zip -C [/code]