- info@configuratori.com
- Italy +39 335 7571048 USA +1 330 714 9301 Poland +48 736 861 972
Rulestream ImportExportPF
What is it?
The ImportExportPF app is aimed to move rules from development/test environment to production or between different DB.
Today if a Rulestream user wants to move a change set, he must migrate the entire DB or re-implement in the production environment manually.
The ImportExportPF app allows the user to select specific PartFamilies or all the PartFamilies belonging to a given Rulestream application and moving them to the destination environment.
The ImportExportPF app is a standalone application reading from a source DB server and writing to destination DB server, without using API’s and/or web services, but creating an intermediate neutral file in MindMap format.
Benefits in using RS Import/Export
- Minimal prerequisites. There is not even the need to have Rulestream installed on the execution machine
- Rulestream application could be tracked into a CVS system. As the application creates a single neutral file with the translation of the RS application, this file could be placed into a CVS system to track modifications, releases etc
- Documentation of Rulestream application. As the neutral file is a mind map file readable by Mind Map graphic editors (for example FreePlane), this is an effective description of the application
- Performances. The DB to DB approach is probably the fastest way to perform the import/export operation
- Rulestream Release independence. A Rulestream application developed in RS 8.17.0 can be moved in a RS 8.16.x or 8.15.x environment
- No Rulestream licenses are copied/overwritten/modified
Process Description
The procedure creates an intermediate file as Mind Map xml file.
The conversion process is a 2 steps process:
Rulestream to Mind Map, Mind Map to Rulestream controlled by a single executable.The Mind Map intermediate file can be used for debug and /or documentation purposes.
Therefore, the entire hierarchical part families structure will be read from Rulestream source DB, stored in the XML intermediate file and deployed into the destination DB. Eventual Categories, Units not existing in the Destination Db are created by the App.
Eventual Connections, Subpart Collections involving the use of Part Families not existing into Destination System, are created but the reference to these foreign Part Families is ignored.