Copyright © Cloud Software Group, Inc. All Rights Reserved

Operations Updater Tool

The Operations Updater tool is used to export xml files to the partner and business agreement configurations.

After migrating from TIBCO BusinessConnect EDI Protocol 5.x to TIBCO BusinessConnect EDI Protocol powered by Instream 6.x, all guidelines, schemas, and validator profiles are not migrated. Some new fields also have to be updated and set after migration, such as root element and the map files that are pertaining to the new Instream engine.

The typical flow of steps after migration is as follows:.

1.	Note that no files are under operations or operations editor after migration.

2.	Run the Operations Updater tool with the export option, so that an XML file is created with all operations and operation bindings information.

3.	Generate all the required files: guidelines, validator profiles (if needed), XSD schemas, and map files as per 6.x standards.

4.	Update the exported XML file with all files information.

5.	Run import again so that all the files information is imported back into the BusinessConnect configuration. After the import, all migrated operations are ready to be used for runtime.

The Operations Updater tool is located in the BC_HOME\protocols\tibedi\tools\operationsupdater directory and consists of the following files:

•	operationsupdater.exe    Executable file to perform the update

•	operationsupdater.tra   Operations Updater .tra file

Using the Operations Updater Tool

This procedure describes how to use the Operations Updater tool.

1.	Make a new guideline file using the EDISIM program.

2.	Use the EDISIM export options to export the XSD and the map files.

3.	Run the operationsupdater tool in export mode to export the current configuration into a readable format.

4.	Modify the exported XML file to map the new guideline, XSD and map files. You can also add the appropriate Root Element name based on the XSD Root Element name.

5.	Import the modified XML file.

After you run operationsupdater.exe by using the command line, the following information is displayed.

---

 

usage: operationsupdater.exe [-jdbcPassword <db password>] [-export] [-help]

-overwrite [-jdbcUser <db user name>] [-import] [-toFile <filepath>] [-fromFile

<filepath>] [-jdbcUrl <jdbc url>] [-jdbcDriver <jdbc driver class>]

----------------------------------------------------------------------

-jdbcPassword <db password> jdbc user password

-export export operation related information

-help print help information

-overwrite whether overwrite the existing files

-jdbcUser <db user name> jdbc user name

-import import operation related information

-toFile <filepath> file path will be used to put the exported

data

-fromFile <filepath> file path will be used to retrieve the xml

content

-jdbcUrl <jdbc url> jdbc URL e.g. jdbc:mysql://localhost:3306/

dbname

-jdbcDriver <jdbc driver class> jdbc driver e.g. com.mysql.jdbc.Driver

 

note:

1. for import/export jdbc options are required, because we have to create

database connection by these options

2. for import option [fromFile] is required, because we need a file path to

retrieve the xml content to do import action

3. for export option [toFile] is optional, if there is no option [toFile] we

will use %BC_HOME%/protocols/tibedi/tools/migration/migration_data.xml instead

4. [overwrite] option only works for command [import]

---

 

Copyright © Cloud Software Group, Inc. All Rights Reserved