OpenText StreamServe 5.6 Upgrading instructions

OpenText StreamServe 5.6

Upgrading instructions

Reference Guide

Rev A

OpenText StreamServe 5.6 Upgrading instructions Reference GuideRev A

Open Text SA40 Avenue Monterey , Luxembourg, Luxembourg L-2163Tel: 35 2 264566 1

Open Text Corporation275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1Tel: +1-519-888-7111Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440Fax: +1-519-888-0677 Email: [email protected]: ftp://ftp.opentext.comFor more information, visit http://www.opentext.com

Copyright ©2012 Open Text Corporation

OpenText is a trademark or registered trademark of Open Text SA and/or Open Text ULC. The list of trademarks is notexhaustive of other trademarks, registered trademarks, product names, company names, brands and service namesmentioned herein are property of Open Text SA or other respective owners.

Disclaimer

No Warranties and Limitation of Liability

Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However,Open Text Corporation and its affiliates accept no responsibility and offer no warranty whether expressed or implied, forthe accuracy of this publication.

3

Contents

About upgrading to OpenText StreamServe 5.6 .......................................................7

Upgrading from 4.1.2 SPx............................................................................................9Upgrading procedures overview .......................................................................................10

RePRINT not included.............................................................................................. 10RePRINT included.................................................................................................... 10

Configuring a 5.6 environment ..........................................................................................11Part A ....................................................................................................................... 11Part B ....................................................................................................................... 11

Upgrading Design Center Projects....................................................................................13Checking the upgraded Project ................................................................................ 13

Physical layers.................................................................................................. 13Multiple Platforms ............................................................................................. 14Barcodes and Intermec IPL driver .................................................................... 15Notifications ...................................................................................................... 15Log file settings................................................................................................. 15Script functions ................................................................................................. 16Connectors ....................................................................................................... 17Startup arguments ............................................................................................ 18Fax drivers ........................................................................................................ 18Profile Manager ................................................................................................ 18Service Broker in 64-bit StreamServe .............................................................. 18SAP features..................................................................................................... 19Scripts accessing data and driver resources .................................................... 19

Migrating RePRINT documents ........................................................................................20Adding document types to Projects .......................................................................... 21

Upgrading from Persuasion SP3 ..............................................................................23Upgrading tools .................................................................................................................24Upgrading procedures overview .......................................................................................25

No StreamStudio included........................................................................................ 25Composer included................................................................................................... 25Collector included..................................................................................................... 26

Configuring a 5.6 environment ..........................................................................................27Part A ....................................................................................................................... 27Part B ....................................................................................................................... 27Part C ....................................................................................................................... 28


Connectors ....................................................................................................... 29Document types................................................................................................ 30Startup arguments ............................................................................................ 31Script functions ................................................................................................. 31Document Broker for FastObjects in 64-bit StreamServe................................. 32Service Broker in 64-bit StreamServe .............................................................. 32

Migrating Composer resources .........................................................................................33Exporting Composer resources................................................................................ 33Importing Composer resources ................................................................................ 33

Upgrading instructionsOpenText StreamServe 5.6 Reference Guide Rev A

4

Migrating SP3 Collector documents..................................................................................34Full migration of an SP3 runtime repository ............................................................. 35

Step 1 – Create a copy of the SP3 runtime repository...................................... 35Step 2 – Create a Migration archive ................................................................. 36Step 3 – Prepare the SP3 runtime repository ................................................... 36Step 4 – Create an application domain for migration........................................ 36Step 5 – Create an Archiver application for migration ...................................... 37Step 6 – Define document types to be used ..................................................... 37Step 7 – Migrate the documents ....................................................................... 37

Incremental migration of additional SP3 documents ................................................ 38Step 1 – Stop the SP3 environment.................................................................. 39Step 2 – Create a repository for incremental migration .................................... 39Step 3 – Prepare the repository for incremental migration ............................... 39Step 4 – Copy the DocumentLock table ........................................................... 39Step 5 – Copy the DocumentTransferStatus table ........................................... 40Step 6 – Update the application domain for migration ...................................... 40Step 7 – Migrate the documents ....................................................................... 40

5.6 deployment after migration ................................................................................ 41Step 1 – Synchronize GUIDs ............................................................................ 41Step 2 – Export Design Center Projects ........................................................... 42Step 3 – Prepare the 5.6 environment .............................................................. 42Step 4 – Deploy export files to StreamServer applications............................... 42Step 5 – Clean up GUIDs in the Migration archive ........................................... 43Step 6 – Connect the Migration archive to the 5.6 application domain............. 43Step 7 – Verify the solution ............................................................................... 43

5.6 deployment during migration ............................................................................. 43Step 1 – Synchronize GUIDs ............................................................................ 44Step 2 – Export Design Center Projects ........................................................... 45Step 3 – Prepare the 5.6 environment .............................................................. 45Step 4 – Create a new Collector archive .......................................................... 45Step 5 – Deploy export files to StreamServers ................................................. 45Step 6 – Start StreamServer applications and archiver .................................... 45Step 7 – Merge the Collector archives.............................................................. 46Step 8 – Verify the solution ............................................................................... 46

Upgrading from Persuasion SP4.............................................................................. 47Database Administration Tool ...........................................................................................48Upgrading procedures overview .......................................................................................49

No StreamStudio included........................................................................................ 49Composer included................................................................................................... 49Composition Center included ................................................................................... 50Collector included ..................................................................................................... 50

Configuring a 5.6 environment ..........................................................................................51Part A........................................................................................................................ 51Part B........................................................................................................................ 51Part C ....................................................................................................................... 52Part D ....................................................................................................................... 52


Composition Center enabled StoryTeller Processes ........................................ 53Document types ................................................................................................ 53Connectors........................................................................................................ 55Startup arguments ............................................................................................ 56


5

Script functions ................................................................................................. 56Document Broker for FastObjects in 64-bit StreamServe................................. 56Service Broker in 64-bit StreamServe .............................................................. 56

Migrating Composer resources .........................................................................................57Exporting Composer resources................................................................................ 57Importing Composer resources ................................................................................ 57

Migrating Composition Center resources..........................................................................58Exporting security data from SP4 runtime repository ............................................... 59Exporting Composition Center resources from SP4 web content repository............ 59Importing security data to 5.6 runtime repository ..................................................... 59Importing Composition Center resources to 5.6 web content repository.................. 60Updating template versions...................................................................................... 60

Upgrading from Persuasion SP5 ..............................................................................61Related documentation .....................................................................................................62Upgrading procedures overview .......................................................................................63

Running parallel installations.................................................................................... 63Creating a 5.6 environment...............................................................................................64

Creating application domains in the 5.6 environment............................................... 64Upgrading application domains using Transport and Migration........................ 64

Deploying web applications...................................................................................... 66Creating a Task Scheduler for template synchronization ......................................... 66Creating repository connections............................................................................... 67

Upgrading Design Center Projects....................................................................................68Checking an upgraded Project ................................................................................. 68

Connectors ....................................................................................................... 68Startup arguments ............................................................................................ 69Script functions ................................................................................................. 69Document Broker for FastObjects in 64-bit StreamServe................................. 70Service Broker in 64-bit StreamServe .............................................................. 70

Cloning and migrating application domains ......................................................................71Migrating repositories........................................................................................................72

Migrating security data ............................................................................................. 72Exporting security data using the DBAT GUI.................................................... 72Importing security data using the DBAT GUI.................................................... 73Exporting security data from command line...................................................... 73Importing security data from command line...................................................... 74

Migrating web content repositories........................................................................... 75Exporting all document definitions using the DBAT GUI .................................. 75Exporting a subset of all document definitions using the DBAT GUI................ 76Importing document definitions using the DBAT GUI ....................................... 76Exporting all document definitions from command line .................................... 77Exporting a subset of all document definitions from command line.................. 78Importing document definitions from command line ......................................... 79

Migrating stored Messages ...................................................................................... 80Exporting stored Messages using the DBAT GUI............................................. 80Importing stored Messages using the DBAT GUI............................................. 81Exporting stored Messages from command line............................................... 81Importing stored Messages from command line............................................... 82

Migrating document definitions (runtime repository)................................................. 83Exporting all document definitions using the DBAT GUI .................................. 83Exporting a subset of all document definitions using the DBAT GUI................ 84


6

Importing document definitions using the DBAT GUI ....................................... 84Exporting all document definitions from command line..................................... 85Exporting a subset of all document definitions from command line .................. 86Importing document definitions from command line ......................................... 87

Command line syntax for repository migration ......................................................... 87Listing all published document definitions ................................................................ 89


7

About upgrading to OpenText StreamServe 5.6

This document contains instructions on how to upgrade to OpenText StreamServe 5.6.

Upgrading from StreamServe 4.1.2 SPx to OpenText StreamServe 5.6

See Upgrading from 4.1.2 SPx on page 9.

Upgrading from Persuasion SP3 to OpenText StreamServe 5.6

See Upgrading from Persuasion SP3 on page 23.





Upgrading from 3.x and pre-4.1.2 SP1

You cannot upgrade 3.x Design Center Projects and pre-4.1.2 SP1 Design Center Projects directly to version 5.6. First you must upgrade the Project to 4.1.2 SP1, and then upgrade the 4.1.2 SP1 version to version 5.6. See Upgrading to StreamServe version 4.1.2 SP1 for instructions.

OpenText StreamServe 5.6 Upgrading instructions Reference Guide Rev A

8About upgrading to OpenText StreamServe 5.6

OpenText StreamServe 5.6Upgrading instructions Reference Guide Rev A

9

Upgrading from 4.1.2 SPx

In this chapter

• Upgrading procedures overview on page 10.• Configuring a 5.6 environment on page 11.• Upgrading Design Center Projects on page 13.• Migrating RePRINT documents on page 20.


10 Upgrading procedures overviewUpgrading from 4.1.2 SPx

Upgrading procedures overviewThe procedures for upgrading from 4.1.2 SPx to version 5.6 depends on wether or not RePRINT is included in the 4.1.2 SPx environment:• The 4.1.2 SPx environment does not include RePRINT. See RePRINT not

included on page 10.• The 4.1.2 SPx environment includes RePRINT. See RePRINT included on

page 10.

RePRINT not includedThe following steps describe how to upgrade if the 4.1.2 SPx environment does not include RePRINT.

RePRINT includedThe following steps describe how to upgrade if the 4.1.2 SPx environment includes RePRINT.

Steps Comments

1 Configure the 5.6 environment.

See the Part A section in Configuring a 5.6 environment on page 11.

2 Backup Design Center Projects.

Backup all Design Center Project files before you upgrade the Design Center Projects.

3 Upgrade Design Center Projects.

See Upgrading Design Center Projects on page 13.

Steps Comments


See the Part A and Part B sections in Configuring a 5.6 environment on page 11.





4 Migrate RePRINT documents.

See Migrating RePRINT documents on page 20.

5 Add document types to Design Center Projects.

See Adding document types to Projects on page 21.


Configuring a 5.6 environment 11Upgrading from 4.1.2 SPx

Configuring a 5.6 environment

Part AThe following applies when upgrading all types of environments.

Connect to the enterprise repository

In Control Center, connect to the site that includes your enterprise repository. See the Control Center user guide for information on how to connect to a site.

Create application domains

In Control Center, create the appropriate application domains for your 5.6 applications. See the Control Center user guide for information on how to create and configure application domains.

Create runtime repositories

You must create one runtime repository for each application domain. See the Control Center user guide for information on how to create runtime repositories.

Add StreamServer applications

Add the appropriate StreamServer applications to the application domains. See the Control Center user guide for information on how to add StreamServer applications.

Part BThe following applies when upgrading environments that include RePRINT.

Add service gateway applications

To be able to use StreamStudio web applications in an application domain, you must add a service gateway application to the application domain. See the Control Center user guide for information on how to add service gateway applications.

Configure application domain for StreamStudio

In addition to the standard application domain configurations, you must also configure the application domain for StreamStudio. See the Control Center user guide for information on how to configure application domains for StreamStudio.

Add StreamStudio web portal

To use the StreamStudio web applications, you must add a StreamStudio web portal in Control Center. The web portal is available to all application domains in a site. Several application domains can share one web portal. See the Control Center user guide for information on how to add StreamStudio web portals.

Connect StreamStudio portal to application domains

You must connect the StreamStudio web portal to the application domains where you want to use the portal. See the Control Center user guide for information on how to connect StreamStudio web portals.


12 Configuring a 5.6 environmentUpgrading from 4.1.2 SPx

Create a Collector archive

In version 5.6, Collector documents are stored in a Collector archive. This means you must create a Collector archive in the 5.6 environment. See the Control Center user guide for information on how to create a Collector archive.

Connect Collector archive to application domains

You must connect the Collector archive to the application domains (runtime repositories) that contain the documents to archive. One Collector archive can be shared by several application domains. See the Control Center user guide for information on how to connect Collector archives.

Create Archiver applications

You must create Archiver applications in the 5.6 application domains. The purpose of the Archiver application is to transfer documents and metadata from the runtime repository to the Collector archive. See the Control Center user guide for information on how to create Archiver applications.


Upgrading Design Center Projects 13Upgrading from 4.1.2 SPx

Upgrading Design Center ProjectsThe following steps describe how to upgrade a Design Center Project.

Checking the upgraded ProjectAfter upgrading, you should verify the configuration of the upgraded Project in Design Center. See the following sections for more information:• Physical layers on page 13• Multiple Platforms on page 14• Barcodes and Intermec IPL driver on page 15• Notifications on page 15• Log file settings on page 15• Script functions on page 16• Connectors on page 17• Startup arguments on page 18• Fax drivers on page 18• Profile Manager on page 18• Service Broker in 64-bit StreamServe on page 18• SAP features on page 19• Scripts accessing data and driver resources on page 19

Physical layers

Platform

When you upgrade a 4.1.2 SPx Project, the Platform is divided into one generic layer and one physical layer. See the Design Center documentation for more information about Platform layers.

Steps Comments

1 Remove multiple Platforms

If you are upgrading a 4.1.2 SPx Project with different Platforms for the development, test and production environment, you should only upgrade the production Platform. This means you must remove the other Platforms and Runtime configurations from the Project before you upgrade.

2 Open the Project in Design Center 5.6.

When you open a Design Center Project in Design Center 5.6, the Project files are automatically upgraded to 5.6. The Design Center log displays information about all upgraded files, and you are prompted to save the files or cancel the upgrade.

3 Check the upgraded Project.

See Checking the upgraded Project on page 13.

4 Save the upgraded Project.

Save the Project and exit Design Center.


14 Upgrading Design Center ProjectsUpgrading from 4.1.2 SPx

Runtime configurations

All Runtime configurations in the Project are also divided into one generic layer and one physical layer. Variables are cleared after each runtime job. If you have more than one runtime configuration, the variables are not available anymore in the Message for the next runtime job. The variable data must be stored in all Messages where you need the variables.See the Design Center documentation for more information about Runtime configuration layers.

Additional layers for the development and test environment

The physical layer is named Production by default, and this layer is meant to be used for the Production environment. During the upgrade, a dialog box opens where you can change the name of the default physical layer. In this dialog box, you can also select to add two additional physical layers to the Project – one for the development environment, and one for the test environment. Both these layers are copies of the upgraded Production layer.

Multiple Platforms

Only upgrade the production Platform

If you are upgrading a 4.1.2 SPx Project with different Platforms for the development, test and production environment, you should only upgrade the production Platform. During the upgrade, the production Platform and Runtime configurations are divided into one generic layer and one physical production layer.

The development and test Platforms

During the upgrade, a dialog box opens where you must select to add two additional physical layers to the Project – one for the development environment, and one for the test environment. Both these layers are copies of the upgraded Production layer.After upgrading, you must edit the development and test layers. The development layer must contain the development environment specific settings, and the test layer must contain the test environment specific settings.

Additional Platforms

If the 4.1.2 SPx Project contains more than three Platforms (development, test, and production) you must:• Add the additional Platforms as physical layers to the Platform in the

upgraded Project. See the Design Center documentation for information on how to add physical layers.

• Configure the environment specific settings for each layer you add.



Barcodes and Intermec IPL driverWhen upgrading a project that uses barcodes and the Intermec IPL driver, you must redesign the barcodes in PageOUT. This driver no longer uses font mapping for creation of barcodes, it uses the enable barcode functionality:1 In PageOUT, right-click the barcode text object, and select Barcode. The

Barcode dialog box opens.2 Select Enable barcodes.3 Select the barcode type, and set optional parameters.

NotificationsNotification settings are specified differently in version 5.6 compared to 4.1.2 SPx. After upgrading, you must verify that the settings are upgraded properly.

Enabling notifications

In version 5.6, you enable notifications on the Job Status tab in the Configure Platform dialog box (generic layer). To enable notifications, select Use notifications.

Specifying what to generate notifications for

In version 5.6, you use the Notifications tab in the Project Export Settings dialog box to specify what to generate notifications for.

Status Messenger

When upgrading from a 4.1.2 SPx Status Messenger Project that uses the StatMess_MultiMessage.sxd file, not all fields are automatically created in the output document. To upgrade the Project correctly you must:• Re-import/add StatMess_MultiMessage.sxd to the resource set.• Open the MessageIN event and import StatMess_MultiMessage.sxd.• Open the process and configure the fields.

Log file settingsThe log file settings in version 5.6 is not configured the same way as in 4.1.2 SPx. In 4.1.2 SPx you used startup arguments to set the following:• Log level (-ll)• Log file name (-log)• Remove log file (-rmlog)In version 5.6, you configure this in the Configure Platform dialog box, and you do it per physical Platform layer.

Log level

In version 5.6 there are five log level settings:• 0 – Severe error messages.• 1 – All error messages.• 2 – All error and warning messages.



• 3 – All error, warning and information messages.• 4 – All error, warning and extended information messages.This means the log level settings are not backwards compatible.

Log file name

In version 5.6 you use the setting Log file name instead of the startup argument -log.

Remove log file

In version 5.6 you use the setting Remove log file when server starts instead of the startup argument -rmlog.

Script functionsThe following script functions are not supported in version 5.6:• ArchiveBegin

• ArchiveEnd

• ArchiveEnable

• ArchiveDisable

• ReplaceJobIDAttribute

• ReplaceJobIDDateAttribute

• ReplaceJobIDNumAttribute

• StoreJobIDAttribute

• StoreJobIDDateAttribute

• StoreJobIDNumAttribute

• GetJobIDAttribute

• GetJobIDDateAttribute

• GetJobIDNumAttribute

• GetJobQueueURI

• GetJobQueueItemId

• GetJobIDJob

• UpdateExternalCompletionStatus

The following script functions are not supported in 64-bit StreamServe:• COMCreateObject

• COMDestroyObject

• COMInvoke

• COMSetProperty

• COMGetProperty

When you start the StreamServer application, a log message for each unsupported script function is displayed in the StreamServer log.



ConnectorsSome connectors are affected when you upgrade to version 5.6. Some connector types are not supported in version 5.6, and in the upgraded Project these connectors are replaced by other connectors. When you open the upgraded Project in Design Center 5.6, a log message is displayed for each affected connector in the Design Center log.

Affected connectors

Connector Comment

Netware NDS Input connector not supported in version 5.6.

Netware Bindery Input connector not supported in version 5.6.

Exchange Input connector not supported in version 5.6.

Serial Input connector not supported in version 5.6.

Service Channel (COM) Input connector not supported in version 5.6.

Service Channel Response (COM)

Input connector not supported in version 5.6.

EmailIN If “Delete mail” was set to “Delete all” before upgrading, this will be changed to “No” after upgrading to 5.6.

FTP input and output FTP input and output connectors are upgraded to a new type of FTP connector that use TCP/IP profiles and authentication profiles to specify host, port, username and password. If you used variables in any of these fields in the old connectors they will not work in the upgraded Project.

ADO connectors Not supported in 64-bit StreamServe. Change to JDBC connectors.

RePRINT Output connector not supported in version 5.6.You must adapt your Design Center Projects to store documents in a Collector archive instead of a RePRINT database. See the Collector user guide for more information.

IXOS Archive in R3 Output connector not supported in version 5.6.Changed to OpenText Archive connectors. See the Connectors user guide for more information about the OpenText Archive connector.

Dazel Output connector not supported in version 5.6.

Netware NDS Output connector not supported in version 5.6.

Netware Bindery Output connector not supported in version 5.6.

TFS Output connector not supported in version 5.6.

TFS for MailOUT Output connector not supported in version 5.6.

HTML Output connector not supported in version 5.6.



Startup argumentsThe startup argument -timer is removed in 5.6.

Fax driversA number of fax drivers are not supported in version 5.6. In the upgraded Project, each unsupported fax driver is replaced by a default driver.

Removed fax drivers

• OMTOOL• CommercePath• FACSys• FastFax• FaxCommander• Faxination• Merkur• MESSAGEManager• VSI-Fax for Notes

Profile ManagerProfile Manager is replaced by the Dispatcher web application. This means Profile Manager solutions are not upgraded.

Service Broker in 64-bit StreamServeService Broker is not supported in 64-bit StreamServe.

SMS Output connector not supported in version 5.6.

WinFaxAdapter Output connector not supported in version 5.6.

Xtrade Output connector not supported in version 5.6.

MSMQ connectors Not supported in 64-bit StreamServe.

Websphere MQ (Legacy) connectors

Not supported in 64-bit StreamServe. Change to new WebSphere MQ connectors.

Lotus Notes connector Not supported in 64-bit StreamServe.

Service Channel (HTTP) connectors

Service Broker is not supported in 64-bit StreamServe.

Connector Comment



SAP features

E-docs incparam file

In 4.1.2 SPx, the incparam file was not included as a resource in Design Center.In version 5.6, the incparam file must be imported to the appropriate resource set in Design Center. The resource type for this file must be RDI Settings.

Scripts accessing data and driver resourcesIn version 5.6, each physical layer has its own working directory. The data and driver directories are moved up one level in the directory hierarchy, and are shared by all working directories (DEV, TEST, etc.)

Figure 1 Directory structure in version 5.6.

If you use scripting to access files in these directories, you must edit the paths in your scripts. The recommendation is to use relative paths.


20 Migrating RePRINT documentsUpgrading from 4.1.2 SPx

Migrating RePRINT documentsDocuments in the RePRINT database must be migrated to a Collector archive in version 5.6. This migration is done using Archive Migration Tool. For more information on how to use Archive Migration Tool, see the Archive Migration Tool user guide.Archive Migration Tool is a wizard that leads you through the configuration of the migration. At the end of the wizard, you start the migration.

To migrate RePRINT documents

1 Select Start > All Programs > OpenText > StreamServe > Utilities > Archive Migration Tool. The Archive Migration Tool opens.

2 Select RePRINT and click Next.3 Select Create new migration and click Next.4 Specify the appropriate connection settings to the RePRINT database and

click Next.5 Specify which documents to migrate:

• Document type – select one or all document types.• Date column – select the appropriate date index to use in the document

search. Select time_of_creation if you are going to migrate all document types.

• Start date – start date index of documents to migrate.• Stop date – stop date index of documents to migrate.

6 Click Next.7 Specify the appropriate connection settings to the Collector archive and

click Next.8 Click Start to start the migration.

To resume an interrupted document migration

This procedure is similar to starting a new migration. The difference is that you must select the option Resume aborted migration instead of Create new migration, and browse to:<User profile>\My Documents\StreamServe Migration\<Date>_<Time>

This folder contains the file migrated_records.txt that is used by Archive Migration Tool when resuming an interrupted migration.

To migrate documents that failed

This procedure is similar to starting a new migration. The difference is that you must select the option Migrate failed documents instead of Create new migration, and browse to:<User profile>\My Documents\StreamServe Migration\<Date>_<Time>

This folder contains the file failed_records.txt that is used by Archive Migration Tool when trying to migrate documents that failed.

If you need to migrate large volumes of documents, you can split the migration into separate chunks, for example by document type.


Migrating RePRINT documents 21Upgrading from 4.1.2 SPx

Adding document types to ProjectsTo be able to store documents in a Collector archive, you must add document type and metadata group resources to your Design Center Projects.

Create a global resource set for document types and metadata

You must create a global resource set for all document types and metadata groups used within an organization. This ensures that all document types, metadata groups, and metadata are unique. To create a global resource set, you can create a separate Design Center Project, and create the global resource set in this Project.

Connect the global resource set to the Design Center Projects

When you have created the global resource set (empty at this stage), you must add it to your Design Center Projects:1 In Design Center, select File > Add to Project. The Add to Project dialog box

opens.2 Click Browse. A file browser opens.3 Browse to and select the global resource set. The global resource set is

added to the Project.

Add document types to the global resource set

The document types and metadata to use are the ones specified in the document types file (*.xml) generated during the migration from the RePRINT database to the Collector archive. You will find this document types file in:<StreamServe installation>\StreamServe\Applications\Archive Migration Tool

1 In Design Center, right-click the global resource set and select Synchronize Document Types. A file browser opens.

2 Select Resources > Synchronize Document Types. A file browser opens. 3 Browse to:

<StreamServe installation>\StreamServe\Applications\Archive Migration Tool

4 Select migration_document_types.xml and click Open. The document types and metadata groups defined in the xml are added to the resource set.

Assign document types to output documents

To be able to store documents in a Collector archive, you must connect the appropriate document types to the output connectors (in Runtime configuration) that stores documents in the Collector archive. 1 Connect the global resource set to the Runtime configurations that includes

the output connectors that stores documents in the Collector archive.2 For each output connector, specify how to store documents in the Collector

archive. See the Collector user guide for more information.


22 Migrating RePRINT documentsUpgrading from 4.1.2 SPx


23

Upgrading from Persuasion SP3

In this chapter

• Upgrading tools on page 24.• Upgrading procedures overview on page 25.• Configuring a 5.6 environment on page 27.• Upgrading Design Center Projects on page 29.• Migrating Composer resources on page 33.• Migrating SP3 Collector documents on page 34.


24 Upgrading toolsUpgrading from Persuasion SP3

Upgrading toolsThis section contains short descriptions of the tools used for upgrading to version 5.6.

Database Administration ToolYou use Database Administration Tool to migrate Composer and Composition Center resources. This tool is also used to clean up GUIDs in the Collector archive when migrating Collector documents.

Tool documentation

For more information on how to use Database Administration Tool, see the Database Administration Tool user guide.

Archive Migration ToolYou use the Archive Migration Tool to prepare the SP3 runtime repository for migration and to generate a configuration file to be used during the migration. The file contains information about the document types to be migrated.Note: The Archive Migration Tool does not perform the actual migration.

Tool documentation

For more information on how to use Archive Migration Tool, see the Archive Migration Tool user guide.

Consolidation of Collector and RePRINT

If you have a Persuasion SP3 Collector environment in parallel with a 3.x/4.x RePRINT environment, and you want to consolidate these archives to a single 5.6 Collector archive, you must migrate the Collector documents before you migrate the RePRINT documents. See Migrating RePRINT documents on page 20 for information.

DocTypeMigratorDocTypeMigrator synchronizes document type GUIDs (Globally Unique Identifiers) in Design Center, runtime repository, and Collector archive. The DocTypeMigrator executable (DocTypeMigrator.exe) is installed in:<StreamServe_installation>\Applications\StreamServer\<version>\Tools\System\

You must migrate the Collector documents before you migrate the RePRINT documents.


Upgrading procedures overview 25Upgrading from Persuasion SP3

Upgrading procedures overviewThe procedures for upgrading from Persuasion SP3 to version 5.6 depends on what is included in the Persuasion SP3 environment:• The Persuasion SP3 environment does not include any StreamStudio

components. See No StreamStudio included on page 25.• The Persuasion SP3 environment includes StreamStudio Composer. See

Composer included on page 25.• The Persuasion SP3 environment includes StreamStudio Collector. See

Collector included on page 26.

Composition Center

Please contact StreamServe for assistance if the Persuasion SP3 environment includes StreamStudio Composition Center.

No StreamStudio includedThe following steps describe how to upgrade if the Persuasion SP3 environment does not include any StreamStudio components.

Composer includedThe following steps describe how to upgrade if the Persuasion SP3 environment includes StreamStudio Composer.

Steps Comments


See the Part A section in Configuring a 5.6 environment on page 27





Steps Comments







4 Migrate Composer resources

See Migrating Composer resources on page 33.


26 Upgrading procedures overviewUpgrading from Persuasion SP3

Collector includedThe following steps describe how to upgrade if the Persuasion SP3 environment includes StreamStudio Collector.

Steps Comments


See the Part A, Part B, and Part C sections in Configuring a 5.6 environment on page 27.





4 Migrate Collector documents

See Migrating SP3 Collector documents on page 34.


Configuring a 5.6 environment 27Upgrading from Persuasion SP3











Part BThe following applies when upgrading environments that include any StreamStudio components.








28 Configuring a 5.6 environmentUpgrading from Persuasion SP3



Part CThe following applies when upgrading environments that include StreamStudio Collector.

Create a Collector archive

In version 5.6, Collector documents are stored in a Collector archive. This means you must create a Collector archive in the 5.6 environment. See the Control Center user guide for information on how to create a Collector archive.






Upgrading Design Center Projects 29Upgrading from Persuasion SP3

Upgrading Design Center ProjectsThe following steps describe how to upgrade a Design Center Project.

Checking the upgraded ProjectAfter upgrading, you should verify the configuration of the upgraded Project in Design Center. See the following sections for more information:• Connectors on page 29.• Document types on page 30.• Startup arguments on page 31• Script functions on page 31• Document Broker for FastObjects in 64-bit StreamServe on page 32• Service Broker in 64-bit StreamServe on page 32

ConnectorsSome connectors are affected when you upgrade to version 5.6. When you open the upgraded Project in Design Center 5.6, a log message is displayed for each affected connector in the Design Center log.

Affected connectors

Steps Comments


When you open a Design Center Project in Design Center 5.6, the Project files are automatically upgraded to 5.6. The Design Center log displays information about all upgraded files, and you are prompted to save the files or cancel the upgrade.Note: This step can take a long time, as global metadata is re-

mapped to shared metadata in 5.6.



3 Save the upgraded Project. Save the Project and exit Design Center.

Connector Comment


FTP input and output FTP input and output connectors are upgraded to a new type of FTP connector that use TCP/IP profiles and authentication profiles to specify host, port, username and password. If you used variables in any of these fields in the old connectors they will not work in the upgraded Project.


30 Upgrading Design Center ProjectsUpgrading from Persuasion SP3

Document types


You must create a global resource set for all document types and metadata groups used within an organization. This ensures that all document types, metadata groups, and metadata are unique. To create a global resource set, you can create a separate Design Center Project, and create the global resource set in this Project.


When you have created the global resource set, you must add it to your Design Center Projects:1 In Design Center, select File > Add to Project. The Add to Project dialog box


added to the Project.4 Connect the global resource set to the appropriate Message and Runtime

configurations in the Project.

Add document type resources to the global resource set

You must generate a document types file (*.xml) that includes all document types and metadata used in your Design Center Projects, and then import this file to the global resource set. This will create all document type and metadata group resources in the global resource set.

IXOS Archive in R3 Output connector not supported in version 5.6.Changed to OpenText Archive connectors. See the Connectors user guide for more information about the OpenText Archive connector.

Collector Reprocess Output connector not supported in version 5.6.If you used Collector Reprocess input connectors in the SP3 Project, you must manually change these connectors to Service Request input connectors. See the Connectors user guide for more information about the Service Request input connector.

ADO connectors Not supported in 64-bit StreamServe. Change to JDBC connectors.

MSMQ connectors Not supported in 64-bit StreamServe.



Lotus Notes connector Not supported in 64-bit StreamServe.



Connector Comment



1 Export and deploy the upgraded (5.6) Design Center Projects that contain the document types you need. Do NOT start the StreamServer applications.

2 In Control Center, right-click the application domain node and select Retrieve Document Types File. A file browser opens.

3 Specify the path and click Save.4 In Design Center, right-click the global resource set and select Synchronize

Document Types. A file browser opens.5 Specify the path to the document types file and click Open. The document

type and metadata group resources are added to the global resource set.

Connect document types to Messages and output connectors

When you have added all document type resources to the global resource set, you must replace the old document type resources connected to Messages and output connectors with the new document type resources in the global resource set.

Remove the old document type resources

When you have replaced the document type resources, you can remove the old document type resources and metadata group resources from your Projects.

Enabling metadata in reusable Composition Center resources

If metadata is used in reusable Composition Center resources (text and rules), you must connect the metadata group that contains the metadata to all document types used in Composition Center. In this circumstance it is recommended to select the option Auto-apply to all Document types when you share the metadata group to document type resources.1 Open the metadata group resource.2 Click Share.3 Select Auto-apply to all Document types and click OK.This replaces the previous Metadata are global option.


Script functions

Function Comment

COMCreateObject Not supported in 64-bit StreamServe.

COMDestroyObject Not supported in 64-bit StreamServe.

COMInvoke Not supported in 64-bit StreamServe.

COMSetProperty Not supported in 64-bit StreamServe.

COMGetProperty Not supported in 64-bit StreamServe.



Document Broker for FastObjects in 64-bit StreamServeDocument Broker for FastObjects is not supported in 64-bit StreamServe. This means Design Center Projects that include Document Broker for FastObjects must be changed to include Document Broker Plus. See Upgrading FastObjects Projects to Document Broker Plus in the Document Broker Plus documentation for more information.



Migrating Composer resources 33Upgrading from Persuasion SP3

Migrating Composer resourcesThe following steps describe how to migrate Composer resources from the SP3 runtime repository to the 5.6 runtime repository.

Exporting Composer resourcesUse Database Administration Tool to export Composer resources and security data (roles, permissions, etc.) from the SP3 runtime repository to a ZIP file. This ZIP file is used as source when importing the resources to the 5.6 runtime repository. Contact StreamServe Support for information on how to export data from earlier versions of Persuasion runtime repositories.Note: Jobs must be finished, and queues must be empty before you export.

To export Composer resources

1 Start Database Administration Tool and connect to the SP3 runtime repository.

2 Click the Runtime Repository button.3 In the Export to field, specify the path to the ZIP file.4 Select to include the Security and Composer areas and click Export. The

resources are exported to the ZIP file.

Importing Composer resourcesUse Database Administration Tool to import Composer resources and security data (roles, permissions, etc.) from the ZIP file to the 5.6 runtime repository.

To import Composer resources

1 Start Database Administration Tool and connect to the 5.6 runtime repository.

2 Click the Runtime Repository button.3 In the Import from field, specify the path to the ZIP file.4 Click Import. The resources are imported from the ZIP file.

Steps Comments

1 Export the Composer resources from the SP3 runtime repository.

Use Database Administration Tool to export Composer resources and security data from the SP3 runtime repository to a ZIP file. See Exporting Composer resources on page 33.

2 Import Composer resources to 5.6 Runtime repository.

Use Database Administration Tool to import Composer resources and security data from the ZIP file to the 5.6 runtime repository. See Importing Composer resources on page 33.


34 Migrating SP3 Collector documentsUpgrading from Persuasion SP3

Migrating SP3 Collector documentsIf the SP3 environment includes StreamStudio Collector, documents are archived in the SP3 runtime repository. In 5.6 these documents must be migrated to a Collector archive.

Consolidation of Collector and RePRINT

If you have a Persuasion SP3 Collector environment in parallel with a 3.x/4.x RePRINT environment, and you want to consolidate these archives to a single 5.6 Collector archive, you must migrate the Collector documents before you migrate the RePRINT documents. See Migrating RePRINT documents on page 20 for information.

Migration tracks

You can follow different tracks when you migrate Collector documents. Which track to follow depends on the downtime allowed in the SP3 environment. The recommendation is to close down the SP3 environment, perform the migration and 5.6 deployment, and finally start the new 5.6 environment. However, this may not always be possible. Before you migrate Collector documents, you must therefore find the answers to the following questions:• Can the SP3 environment be shut down during migration?

Note: “Shut down” means “stop using forever”.

• Can I wait until migration is completed before I start using the 5.6 environment?

The answers to these questions determine which track to follow. See the table below.

You must migrate the Collector documents before you migrate the RePRINT documents.

If you... You must follow this track...

• Can shut down the SP3 environment when you migrate the documents.

• Can wait until migration is completed before you start using the 5.6 environment.

1 Run a full migration. See Full migration of an SP3 runtime repository on page 35.

2 Deploy. See 5.6 deployment after migration on page 41.


• Can shut down the SP3 environment when you migrate the documents.

• Cannot wait until migration is completed before you start using the 5.6 environment.


2 Deploy. See 5.6 deployment during migration on page 43.


Migrating SP3 Collector documents 35Upgrading from Persuasion SP3

Full migration of an SP3 runtime repository

Steps included

• Step 1 – Create a copy of the SP3 runtime repository on page 35.• Step 2 – Create a Migration archive on page 36.• Step 3 – Prepare the SP3 runtime repository on page 36.• Step 4 – Create an application domain for migration on page 36.• Step 5 – Create an Archiver application for migration on page 37.• Step 6 – Define document types to be used on page 37.• Step 7 – Migrate the documents on page 37.

Step 1 – Create a copy of the SP3 runtime repositoryYou perform a full migration on a copy of the SP3 runtime repository. This means the original SP3 runtime repository can still be used in the SP3 environment while the already archived documents are migrated from the repository copy.If the SP3 environment is up and running during the migration period, new documents may be archived in the original SP3 runtime repository. These documents must be migrated using incremental migration, see Incremental migration of additional SP3 documents on page 38.

To create a copy of the SP3 runtime repository

1 Make a complete backup of the SP3 runtime repository.2 Restore the backup of the SP3 runtime repository, using a different

database name or a different location.


• Cannot shut down the SP3 environment when you migrate the documents.

• Can wait until migration is completed before you start using the 5.6 environment.


2 Run an incremental migration. See Incremental migration of additional SP3 documents on page 38.

3 Deploy. See 5.6 deployment after migration on page 41.


• Cannot shut down the SP3 environment when you migrate the documents.

• Cannot wait until migration is completed before you start using the 5.6 environment.


2 Run an incremental migration. See Incremental migration of additional SP3 documents on page 38.

3 Deploy. See 5.6 deployment during migration on page 43.



Step 2 – Create a Migration archiveThe Migration archive is the target for the migrated documents.

To create a Migration archive

1 Open Control Center and create a Collector archive.2 Open the DBMS (Database Management System) for the database server

and adjust the following database properties:• Make the Collector archive the same size as the SP3 runtime

repository.• Place the database files on the most suitable disks.• Adjust the logging level to a minimum.• Disable backup routines.• Optimize for writing to disk.

Step 3 – Prepare the SP3 runtime repositoryYou use the Archive Migration Tool to prepare the SP3 runtime repository for migration and to generate a document types file to be used during the migration. The document types file contains information about the document types to be migrated.

To prepare the SP3 runtime repository

1 Open the Archive Migration Tool. 2 Select Collector as the migration source. 3 Specify the copy of the SP3 runtime repository as the source database.4 Specify the Migration archive as the target database.5 Click Start.

The SP3 runtime repository is upgraded to 5.6 and the document types file (migration_document_types.xml) is created in the following directory:<StreamServe installation>\StreamServe\Applications\Archive Migration Tool

Step 4 – Create an application domain for migrationYou use a dedicated application domain for migration. This application domain must include at least one Archiver application that performs the actual migration. The application domain must use the upgraded SP3 runtime repository, and must be linked to the Migration archive.

Prerequisites

You must have full access (user name and password) to the upgraded SP3 runtime repository. If you do not know the user name or password, you can access the repository as an administrator user.

To create an application domain for migration

1 In Control Center, create a new application domain.



2 Open the Application Domain Editor and specify the upgraded SP3 runtime repository as runtime repository.

3 Link the Migration archive to the application domain for migration.

Step 5 – Create an Archiver application for migrationYou must create and configure at least one Archiver application in the application domain for migration. The Archiver application will perform the actual migration.

To create an Archiver application

1 In Control Center, create a new Archiver application in the application domain for migration.

2 Right-click the Archiver application and select Configuration. The Configuration dialog box opens.

3 Add a new Migration task and configure the following:• Name – enter the appropriate name.• Document type – select document type (All if one Archiver application

is used, or <document type> if several Archiver applications are used).• Keep the other default settings.

Step 6 – Define document types to be usedThe Archiver application running the migration task needs information about the document types of the documents to be migrated. This information is provided by the migration_document_types.xml file, created by the Archive Migration Tool (see Step 3 – Prepare the SP3 runtime repository on page 36). You must copy the file to the working directory of the Archiver application.

To define the document types

1 In your file management system, copy migration_document_types.xml from the Archive Migration Tool working directory:<StreamServe installation>\StreamServe\Applications\Archive Migration Tool

2 Paste the file into the working directory of the Archiver application. For example:C:\ManagementGateway\1.0\root\application\<Archiver>

Step 7 – Migrate the documentsNow you can start the migration.

You get the most control if you migrate one document type at a time.Create an Archiver application for each document type and let the applications work in parallel or in sequence. The total throughput will not increase, but you may gain some processing time.



Before you start, you should set a high log level to verify that all works fine. If everything is OK, you should decrease the log level in order to save CPU and disk.

To migrate documents

1 In Control Center, open the Archiver configuration dialog box and set the log level to 3.

2 Start the Archiver application.3 Check the Archiver log to verify that all is OK.4 If all is OK, change the log level to 2 and let the job continue.

The Archiver application now performs the configured migration task and the SP3 documents are migrated to the Migration archive.

To monitor the migration

There are several ways to monitor a migration. For example, you can execute a query regularly to count the documents in the archive. You can use the Windows Task Manager (or a similar tool) to monitor the CPU load and the memory usage during the migration. For the CPU load on the database server, you want the database server to use as much as possible from as many processor cores as possible.

Incremental migration of additional SP3 documentsIn this scenario, a full snapshot of the SP3 runtime repository has already been migrated (see Full migration of an SP3 runtime repository on page 35). You must now migrate any additional SP3 documents that have been archived after the full migration was performed.

Steps included

• Step 1 – Stop the SP3 environment on page 39.• Step 2 – Create a repository for incremental migration on page 39.• Step 3 – Prepare the repository for incremental migration on page 39.• Step 4 – Copy the DocumentLock table on page 39.• Step 5 – Copy the DocumentTransferStatus table on page 40.• Step 6 – Update the application domain for migration on page 40.• Step 7 – Migrate the documents on page 40.

By default, an Archiver application migrates 100 documents at a time (segment size), using 10 threads. Depending on the server hardware, you may want to adjust these parameters. Monitor the CPU load and the memory usage. If you experience that the hardware is under-utilized, try a substantially higher value for the segment size, for example 3000. You change the segment size setting in the advanced configuration of the Archiver application.



Step 1 – Stop the SP3 environmentBefore you do anything else, you must stop the SP3 environment to make sure no new documents are archived during the migration.

To stop the SP3 environment

In Control Center, stop all running applications in the SP3 environment.

Step 2 – Create a repository for incremental migrationYou need a new copy of the SP3 runtime repository to be used in the incremental migration. Since the SP3 runtime repository copy used in the full migration is also used in the incremental migration, you must have access to both these repositories at the same time.

Comments

From now on, the SP3 runtime repository copy used in full migration is called full repository, and the SP3 runtime repository copy used in incremental migration is called incremental repository.

To create an incremental repository

1 Make a new complete backup of the SP3 runtime repository.2 Restore the backup repository to a different database name than the backup

repository for full migration.

Step 3 – Prepare the repository for incremental migrationYou use Archive Migration Tool to prepare the incremental repository for migration and to generate a document types file to be used during the migration. The document types file contains information about the document types to be migrated.

To prepare the incremental repository

1 Open Archive Migration Tool. 2 Select Collector as the migration source. 3 Specify the incremental repository as the source database.4 Specify the Migration archive as the target database.5 Click Start.

The incremental repository is upgraded to 5.6 and a document types file (migration_document_types.xml) is created in the following directory:<StreamServe installation>\StreamServe\Applications\Archive Migration Tool

Step 4 – Copy the DocumentLock tableThe incremental repository must have the same DocumentLock table as the full repository. This means you must copy the contents of this table from the full repository to the incremental repository.



To copy the DocumentLock table

The DocumentLock table contains one single row with data. In the DBMS, you can copy the row from the full repository and paste it into the DocumentLock table in the incremental repository.

Step 5 – Copy the DocumentTransferStatus tableDuring an incremental migration, the Archiver finds all documents (that is, all documents that are already migrated during the full migration and all additional SP3 documents that are yet not migrated).By copying the contents of the DocumentTransferStatus table from the full repository to the incremental repository, you make the Archiver application aware of which documents are already migrated. The Archiver application will then only migrate the additional SP3 documents during the incremental migration.Note: There is a duplicate check when the documents are inserted into the new

Collector archive, ensuring that each document is only archived once.

To copy the DocumentTransferStatus table

In your DBMS, use the proper feature (for example, the Import feature for SQL Server) to copy all rows from the DocumentTransferStatus table in the full repository to the DocumentTransferStatus table in the incremental repository.

Step 6 – Update the application domain for migrationWhen you run the incremental migration, you can use the same dedicated application domain and the same Archiver application as you used in the full migration. However, before you start the migration, you must change the runtime repository from the full repository to the incremental repository.Note: If you create a new application domain, you must connect the application

domain to the same Collector archive as in the full migration.

To change the runtime repository

1 In Control Center, open the Application Domain Editor for the application domain.

2 Change the runtime repository to the incremental repository.

Step 7 – Migrate the documentsIn Control Center, start the Archiver application. The Archiver application spends a few minutes analyzing the DocumentTransferStatus table, and then migrates the additional SP3 documents to the 5.6 Collector archive.When the migration is finished, all SP3 documents have been migrated and the SP3 environment can be permanently shut down.



5.6 deployment after migrationUse this scenario when you do not need to start using version 5.6 until all of SP3 documents are migrated into the 5.6 Collector archive.

Steps included

• Step 1 – Synchronize GUIDs on page 41.• Step 2 – Export Design Center Projects on page 42.• Step 3 – Prepare the 5.6 environment on page 42.• Step 4 – Deploy export files to StreamServer applications on page 42.• Step 5 – Clean up GUIDs in the Migration archive on page 43.• Step 6 – Connect the Migration archive to the 5.6 application domain on page 43.• Step 7 – Verify the solution on page 43.

Step 1 – Synchronize GUIDsUse the DocTypeMigrator tool to replace the GUIDs in the upgraded Projects with those extracted from the SP3 runtime repository by the Archive Migration Tool (see Step 3 – Prepare the SP3 runtime repository on page 36). This will replace all GUIDs in the Projects, re-using as many of the SP3 GUIDs as possible.Note: The DocTypeMigrator tool implements the SP4 model for metadata. If

you wish to use any other model, you must modify the GUIDs manually. Contact StreamServe Support for instructions.

To run DocTypeMigrator

Use the following syntax to run DocTypeMigrator:DocTypeMigrator ProjectPath DocumentTypePath -UPGRADE

To check errors and warnings

Errors and warnings are logged to the command prompt.

ProjectPath The path to the Design Center Project(s). If the path includes several Projects (in sub-directories), all Projects are affected.

DocumentTypePath The path to migration_document_types.xml:<StreamServe installation>\StreamServe\Applications\Archive Migration Tool\migration_document_types.xml

Message when incorrect ProjectPath is specified

Could not open path to DesignCenter project folder <path>

Upgrade finished, there were errors, check the log

Message when incorrect DocumentTypePath is specified

Could not find the DocumentType file <path>




Step 2 – Export Design Center ProjectsOpen and export all Design Center Projects. Before you export you can verify that the GUIDs are updated correctly. To do this, you can open the document type resources and compare GUIDs in the resource editor with the corresponding GUIDs in the document type xml extracted from the SP3 runtime repository.

Step 3 – Prepare the 5.6 environmentIn your 5.6 environment, make sure you have an Archiver application that handles all document types. See Part C in Configuring a 5.6 environment on page 27.

Step 4 – Deploy export files to StreamServer applicationsDeploy the exported Design Center Projects to the corresponding StreamServer applications.

When you have deployed the last Project you must locate the document_types.xml generated by the deployment. You will find it in the working directory of the StreamServer application to which the last Project was deployed. This file is used in the next step to clean up GUIDs in the Collector archive.

Actions

1 In Control Center, deploy the first Project to its StreamServer application.Note: Do not start the StreamServer application at this stage!

2 Deploy all other Projects.Note: Do not start the StreamServer application at this stage!

3 Locate document_types.xml.

Message when DocumentTypePath is specified as folder

Could not read the DocumentType file <path>


Messages when resources could not be opened in Read/Write

Could not open resource: <path>


Upgrade finished, there were warnings, check the log

Do not start the StreamServer applications at this stage. If you do, you will damage the runtime repository.



Step 5 – Clean up GUIDs in the Migration archiveIt is very important that you clean up the GUIDs in the Migration archive. The cleaned-up Migration archive can then be used in the 5.6 environment.

To clean up the GUIDs

1 Make a backup of the Migration archive.2 Open Database Administration Tool and connect to the Migration archive. 3 Click the Metadata button and load the document_types.xml (see the

previous procedure).4 Inspect the proposed changes and apply them.

Step 6 – Connect the Migration archive to the 5.6 application domain

When you have cleaned up the GUIDs in the Migration archive, you can connect it to the 5.6 application domain.

To connect the Migration archive to the 5.6 application domain

In Control Center, connect the Migration archive to the 5.6 application domain.

Step 7 – Verify the solution1 Start the StreamServer and Archiver applications and run the Projects. 2 Process and archive a few documents. 3 Verify that the documents are properly archived in the Migration archive.

You now have an 5.6 Collector archive that contains all your SP3 Collector documents and is ready to be filled with new 5.6 documents.

5.6 deployment during migrationUse this scenario if you must start using version 5.6 while the migration of the SP3 documents is still in progress.

Included steps

• Step 1 – Synchronize GUIDs on page 44.• Step 2 – Export Design Center Projects on page 45.• Step 3 – Prepare the 5.6 environment on page 45.• Step 4 – Create a new Collector archive on page 45.• Step 5 – Deploy export files to StreamServers on page 45.• Step 6 – Start StreamServer applications and archiver on page 45.• Step 7 – Merge the Collector archives on page 46.• Step 8 – Verify the solution on page 46



Step 1 – Synchronize GUIDsUse the DocTypeMigrator tool to replace the GUIDs in the upgraded Projects with those extracted from the SP3 runtime repository by the Archive Migration Tool (see Step 3 – Prepare the SP3 runtime repository on page 36). This will replace all GUIDs in the Projects, re-using as many of the SP3 GUIDs as possible.Note: The DocTypeMigrator tool implements the SP4 model for metadata. If you

wish to use any other model, you must modify the GUIDs manually. Contact StreamServe Support for instructions.

To run DocTypeMigrator

Use the following syntax to run DocTypeMigrator:DocTypeMigrator ProjectPath DocumentTypePath -UPGRADE

To check errors and warnings

Errors and warnings are logged to the command prompt.

ProjectPath The path to the Design Center Project(s). If the path includes several Projects (in sub-directories), all Projects are affected.

DocumentTypePath The path to migration_document_types.xml:<StreamServe installation>\StreamServe\Applications\Archive Migration Tool\migration_document_types.xml

Message when incorrect ProjectPath is specified

Could not open path to DesignCenter project folder <path>


Message when incorrect DocumentTypePath is specified

Could not find the DocumentType file <path>


Message when DocumentTypePath is specified as folder

Could not read the DocumentType file <path>


Messages when resources could not be opened in Read/Write



Upgrade finished, there were warnings, check the log



Step 2 – Export Design Center ProjectsOpen and export all Design Center Projects. Before you export you can verify that the GUIDs are updated correctly. To do this, you can open the document type resources and compare GUIDs in the resource editor with the corresponding GUIDs in the document type xml extracted from the SP3 runtime repository.

Step 3 – Prepare the 5.6 environmentIn your 5.6 environment, make sure you have an Archiver application that handles all document types. See Part C in Configuring a 5.6 environment on page 27.

Step 4 – Create a new Collector archiveSince migration to the Migration archive is in progress, you need a new 5.6 Collector archive that is independent of the migration in progress. The Migration archive and this new 5.6 archive will later be merged. In the instructions below, this new 5.6 Collector archive is referred to as the New archive.

To create a new Collector archive

1 In Control Center, create the New archive.2 Link the New archive to the 5.6 application domain.

Step 5 – Deploy export files to StreamServersDeploy the exported Design Center Projects to the corresponding StreamServer applications (in the 5.6 application domain).

To deploy the export files

1 In Control Center, deploy the first Project to its StreamServer application.2 Deploy all other Projects.

Step 6 – Start StreamServer applications and archiverNow you can start the StreamServer applications and the Archiver application.

Actions

1 In Control Center, start the StreamServer applications.2 Start the Archiver application.3 Process and archive a few documents and verify that they end up in the

New archive.Now you have an 5.6 Collector archive that is ready to be filled with 5.6 documents. Your 5.6 StreamServer applications can be up and running and archive documents in the New archive while migration to the Migration archive is in progress.



Step 7 – Merge the Collector archivesThe New archive contains the GUIDs required in the version 5.6 environment. You must consider whether to merge the Migration archive into the New archive or vice versa:• If you copy the documents from the Migration archive to the New archive,

you do not have to modify the GUIDs. • If you copy the documents from the New archive to the Migration archive,

the GUIDS in the Migration archive must be cleaned up. See Step 5 – Clean up GUIDs in the Migration archive on page 43.

To merge the Collector archives

1 When it fits your schedule, stop the StreamServer applications running the upgraded Projects.

2 In your DBMS, use the proper feature (for example, the Import feature for SQL Server) to merge the Collector archives.

Step 8 – Verify the solution1 Start the StreamServer applications and run the Projects. 2 Process and archive a few documents. 3 Verify that the documents are properly archived.


47


In this chapter

• Database Administration Tool on page 48.• Upgrading procedures overview on page 49.• Configuring a 5.6 environment on page 51.• Upgrading Design Center Projects on page 53.• Migrating Composer resources on page 57.• Migrating Composition Center resources on page 58.


48 Database Administration ToolUpgrading from Persuasion SP4

Database Administration ToolYou use Database Administration Tool to:• Migrate Composer resources from the SP4 runtime repository to the 5.6

runtime repository.• Migrate security data from the SP4 runtime repository to the 5.6 runtime

repository.• Migrate Composition Center resources from the SP4 web content repository

to the 5.6 web content repository.

Tool documentation

For more information on how to use Database Administration Tool, see the Database Administration Tool user guide.



Upgrading procedures overviewThe procedures for upgrading from Persuasion SP4 to version 5.6 depends on what is included in the Persuasion SP4 environment:• The Persuasion SP4 environment does not include any StreamStudio

components. See No StreamStudio included on page 49.• The Persuasion SP4 environment includes StreamStudio Composer. See

Composer included on page 49.• The Persuasion SP4 environment includes StreamStudio Composition

Center. See Composition Center included on page 50.• The Persuasion SP4 environment includes StreamStudio Collector. See

Collector included on page 50.

No StreamStudio includedThe following steps describe how to upgrade if the Persuasion SP4 environment does not include any StreamStudio components.

Composer includedThe following steps describe how to upgrade if the Persuasion SP4 environment includes StreamStudio Composer.

Steps Comments


See the Part A section in Configuring a 5.6 environment on page 51





Steps Comments







4 Migrate Composer resources

See Migrating Composer resources on page 57.


50 Upgrading procedures overviewUpgrading from Persuasion SP4

Composition Center includedThe following steps describe how to upgrade if the Persuasion SP4 environment includes StreamStudio Composer.

Collector includedThe following steps describe how to upgrade if the Persuasion SP4 environment includes StreamStudio Collector.

Steps Comments


See the Part A, Part B, and Part C sections in Configuring a 5.6 environment on page 51.





4 Migrate Composition Center resources

See Migrating Composition Center resources on page 58.

Steps Comments


See the Part A, Part B, and Part D sections in Configuring a 5.6 environment on page 51.






Configuring a 5.6 environment 51Upgrading from Persuasion SP4











Part BThe following applies when upgrading environments that include any StreamStudio components.








52 Configuring a 5.6 environmentUpgrading from Persuasion SP4



Part CThe following applies when upgrading environments that include StreamStudio Composition Center.

Configure application domain for Composition Center

In addition to the standard StreamStudio application domain configuration, you must also specify the database settings for the web content repository and the connection settings to access the repository. See the Control Center user guide for information on how to configure application domains for Composition Center.

Create web content repository

To be able to run Composition Center, you must create a web content repository. See the Control Center user guide for information on how to create a web content repository.Note: If you have several StreamStudio portals running, and if these portals are

deployed to the same web server, they cannot share the same web content repository.

Part DThe following applies when upgrading environments that include StreamStudio Collector.







Upgrading Design Center ProjectsThe following steps describe how to upgrade an SP4 Design Center Project to 5.6.

Checking the upgraded ProjectAfter upgrading, you should verify the configuration of the upgraded Project in Design Center. See the following sections for more information:• Composition Center enabled StoryTeller Processes on page 53• Document types on page 53.• Connectors on page 55.• Startup arguments on page 56• Script functions on page 56• Document Broker for FastObjects in 64-bit StreamServe on page 56• Service Broker in 64-bit StreamServe on page 56

Composition Center enabled StoryTeller ProcessesIf the Project includes Composition Center enabled StoryTeller Processes, the template versions are set to -1 in the upgraded (5.6) Project. You must temporarily set all template versions to 1 before you export and deploy the Project. You will later change to the correct template versions after you have migrated the web content repository resources.

To set all template versions to 1

1 Right-click the Project node and select Update Composition Center template versions.

2 Select Set all Composition Center template versions to 1 and click OK.

Document types


You must create a global resource set for all document types and metadata groups used within an organization. This ensures that all document types, metadata groups, and metadata are unique.

Steps Comments


When you open a Design Center Project in Design Center 5.6, the Project files are automatically upgraded to 5.6. The Design Center log displays information about all upgraded files, and you are prompted to save the files or cancel the upgrade.



3 Save the upgraded Project. Save the Project and exit Design Center.



To create a global resource set, you can create a separate Design Center Project, and create the global resource set in this Project.


When you have created the global resource set, you must add it to your Design Center Projects:1 In Design Center, select File > Add to Project. The Add to Project dialog box


added to the Project.4 Connect the global resource set to the appropriate Message and Runtime

configurations in the Project.

Add document type resources to the global resource set

You must generate a document types file (*.xml) that includes all document types and metadata used in your Design Center Projects, and then import this file to the global resource set. This will create all document type and metadata group resources in the global resource set.1 Export and deploy the upgraded (5.6) Design Center Projects that contain

the document types you need. Do NOT start the StreamServer applications.2 In Control Center, right-click the application domain node and select

Retrieve Document Types File. A file browser opens.3 Specify the path and click Save.4 In Design Center, right-click the global resource set and select Synchronize

Document Types. A file browser opens.5 Specify the path to the document types file and click Open. The document

type and metadata group resources are added to the global resource set.

Connect document types to Messages and output connectors

When you have added all document type resources to the global resource set, you must replace the old document type resources connected to Messages and output connectors with the new document type resources in the global resource set.

Remove the old document type resources

When you have replaced the document type resources, you can remove the old document type resources and metadata group resources from your Projects.

Enabling metadata in reusable Composition Center resources

If metadata is used in reusable Composition Center resources (text and rules), you must connect the metadata group that contains the metadata to all document types used in Composition Center. In this circumstance it is recommended to select the option Auto-apply to all Document types when you share the metadata group to document type resources.1 Open the metadata group resource.2 Click Share.3 Select Auto-apply to all Document types and click OK.This replaces the previous Metadata are global option.



ConnectorsSome connectors are affected when you upgrade to version 5.6. When you open the upgraded Project in Design Center 5.6, a log message is displayed for each affected connector in the Design Center log.Affected connectors

Connector Comment


FTP input and output

FTP input and output connectors are upgraded to a new type of FTP connector that use TCP/IP profiles and authentication profiles to specify host, port, username and password. If you used variables in any of these fields in the old connectors they will not work in the upgraded Project.

Preview connectors

The technology for previewing documents in Composition Center is redesigned. The HTTP connector is replaced by a new preview functionality based on web service requests.

Remove separate physical layer for preview

If the SP4 Project contained a separate physical Platform layer for the preview functionality, you must remove that layer from the upgraded Design Center Project.

Enable previewing using default preview connectors

To enable the new preview functionality for a Message using default preview connectors, you must:1 Activate the Runtime configuration view that includes the Message.2 Right-click the Message and select Service.

The Service –<Message name> dialog box opens.3 Select Use default preview connectors.4 In the Service name text box, enter a descriptive name for the service.

The name must be unique within the application domain.5 Click OK.

Enable previewing using custom preview connectors

For information about how to invoke Messages through service requests and when to create preview output connectors manually, see the Composition Center documentation.

ADO connectors

Not supported in 64-bit StreamServe. Change to JDBC connectors.

MSMQ connectors

Not supported in 64-bit StreamServe.






Script functions



Lotus Notes connector




Connector Comment

Function Comment







Migrating Composer resources 57Upgrading from Persuasion SP4

Migrating Composer resourcesThe following steps describe how to migrate Composer resources from the SP4 runtime repository to the 5.6 runtime repository.

Exporting Composer resourcesUse Database Administration Tool to export Composer resources and security data from the SP4 runtime repository to a ZIP file. This ZIP file is used as source when importing the resources to the 5.6 runtime repository. Contact StreamServe Support for information on how to export data from earlier versions of Persuasion runtime repositories.Note: Jobs must be finished, and queues must be empty before you export.

To export Composer resources

1 Start Database Administration Tool and connect to the SP4 runtime repository.

2 Click the Runtime Repository button.3 In the Export to field, specify the path to the ZIP file.4 Select to include the Security and Composer areas and click Export. The

resources are exported to the ZIP file.

Importing Composer resourcesUse Database Administration Tool to import Composer resources and security data from the ZIP file to the 5.6 runtime repository.

To import Composer resources


2 Click the Runtime Repository button.3 In the Import from field, specify the path to the ZIP file.4 Click Import. The resources are imported from the ZIP file.

Steps Comments

1 Export the Composer resources from the SP4 runtime repository.

Use Database Administration Tool to export Composer resources and security data from the SP4 runtime repository to a ZIP file. See Exporting Composer resources on page 57.

2 Import Composer resources to the 5.6 Runtime repository.

Use Database Administration Tool to import Composer resources and security data from the ZIP file to the 5.6 runtime repository. See Importing Composer resources on page 57.


58 Migrating Composition Center resourcesUpgrading from Persuasion SP4

Migrating Composition Center resourcesThe following steps describe how to migrate Composition Center resources from the SP4 web content repository to the 5.6 web content repository.

Steps Comments

1 Export security data from the SP4 runtime repository.

Use Database Administration Tool to export security data from the SP4 runtime repository to a ZIP file. See Exporting security data from SP4 runtime repository on page 59.

2 Export the Composition Center resources from the SP4 web content repository.

Use Database Administration Tool to export document definitions and related resources from the SP4 web content repository to a ZIP file. See Exporting Composition Center resources from SP4 web content repository on page 59.

3 Import security data to the 5.6 runtime repository.

Use Database Administration Tool to import security data from the ZIP file to the 5.6 runtime repository. See Importing security data to 5.6 runtime repository on page 59.

4 Find document types file used in SP4 environment.

Before you can import Composition Center resources to the 5.6 web content repository, you must find the SP4 document types file (document_types.xml) that includes all document types. You must use this file when you import Composition Center resources to the 5.6 web content repository.

5 Import Composition Center resources to the 5.6 web content repository.

Use Database Administration Tool to import document definitions and related resources from the ZIP file to the 5.6 web content repository. See Importing Composition Center resources to 5.6 web content repository on page 60.

6 Update template versions.

Update the versions of StoryTeller Processes that are used as templates in Composition Center. See Updating template versions on page 60.

7 Start StreamServer applications.

Start the StreamServer applications in the 5.6 environment, and wait for the web content repository and runtime repository to get synchronized.

8 Re-publish document definitions in Composition Center.

All published document definitions are set to Unpublished after the import. You must therefore re-publish the document definitions in Composition Center. See the Composition Center documentation for information.


Migrating Composition Center resources 59Upgrading from Persuasion SP4

Exporting security data from SP4 runtime repositoryUse Database Administration Tool to export security data from the SP4 runtime repository to a ZIP file. This ZIP file is used as source when importing the security data to the 5.6 runtime repository.

To export security data


2 Click the Runtime repository button.3 Make sure only the Security area is selected.4 In the Export to field, specify the path to the ZIP file.5 Click Export. The resources are exported to the ZIP file.

Exporting Composition Center resources from SP4 web content repository

Use Database Administration Tool to export document definitions and related resources from the SP4 web content repository to a ZIP file. This ZIP file is used as source when importing the Composition Center resources to the 5.6 web content repository.

To export Composition Center resources

1 Start Database Administration Tool and connect to the SP4 web content repository.

2 Click the Web content repository button.3 In the Export to field, specify the path to the ZIP file.4 Click Export. The resources are exported to the ZIP file.

Importing security data to 5.6 runtime repositoryUse Database Administration Tool to import security data from the ZIP file to the 5.6 runtime repository.

To import security data


2 Click the Runtime repository button.3 In the Import from field, specify the path to the ZIP file.4 Click Import. The security data is imported from the ZIP file.


60 Migrating Composition Center resourcesUpgrading from Persuasion SP4

Importing Composition Center resources to 5.6 web content repository

Use Database Administration Tool to import document definitions and related resources from the ZIP file to the 5.6 web content repository.

To import Composition Center resources

1 Start Database Administration Tool and connect to the 5.6 web content repository.

2 Click the Web content Repository button.3 In the Import from field, specify the path to the ZIP file.4 Click Import. The Import dialog box opens.5 Browse to and select the SP4 document types file (document_types.xml).6 Click OK. The resources are imported from the ZIP file.

Updating template versionsAfter importing document definitions and related resources, you must update the versions of the StoryTeller Processes that are used as templates in Composition Center. You must do this in all Design Center Projects that contain this type of StoryTeller Processes.

Version information file

When you update, you must use a version information file:imported-templateversions-<repositoryname>-<schemaversion>-<yyyyMMddHHmmss>.xml

This file is created during the import to the web content repository, and you will find it in:<user_home>\dbadmintool-files\import

To update template versions in a Design Center Project

1 In the Project browser in Design Center, right-click the Project node and select Update Composition Center template versions. The Set Composition Center template version dialog box opens.

2 Select Update all Composition Center template versions from file.3 Browse to and select the version information file to use (see Version

information file above) and click OK.


61


In this chapter

• Related documentation on page 62• Upgrading procedures overview on page 63• Creating a 5.6 environment on page 64• Upgrading Design Center Projects on page 68• Cloning and migrating application domains on page 71• Migrating repositories on page 72


62 Related documentationUpgrading from Persuasion SP5

Related documentationIn addition to this document, you can find information related to upgrading and migration in the following OpenText StreamServe 5.6 documents:

• Control Center User GuideInformation about how to create and configure application domains, deploy web applications, configure repository connections etc.

• Database Administration Tool User GuideInformation about how to migrate repositories.

• Transport and migration Reference GuideInformation about how to clone and migrate application domains.

These documents are available at OpenText Knowledge Center. You can also find this documentation in the OpenText StreamServe 5.6 online help:http://onlinehelp.streamserve.com/5.6/en/index.html


http://onlinehelp.streamserve.com/5.6/en/index.html


Upgrading procedures overview 1 If you have an earlier SP5 version than hotfix 1684 you must apply hotfix

1684 or later to the SP5 installation.2 Install 5.6 in parallel with SP5. See Running parallel installations on page 63.3 Create a new 5.6 environment in parallel with the SP5 environment. See

Creating a 5.6 environment on page 64.4 Pack the SP5 Design Center projects and save the Project packages in the

appropriate folders in the 5.6 environment.5 Upgrade the Project packages to 5.6. See Upgrading Design Center Projects on

page 68.6 Export the upgraded Projects (not needed if you used Transport and

Migration to upgrade the Project packages).7 Create the application domains and applications in the 5.6 environment.

See Creating application domains in the 5.6 environment on page 64.8 Create new runtime repositories and web content repositories for the 5.6

application domains.9 Deploy the Project exports to the StreamServer applications (not needed if

you used Transport and Migration to upgrade the Project packages).10 Start the StreamServer applications and verify that there are no errors.11 Migrate the security data from the SP5 runtime repositories to the 5.6

runtime repositories. See Migrating security data on page 72.12 Migrate document definitions and related resources from the SP5 web

content repositories to the 5.6 web content repositories. See Migrating web content repositories on page 75.

13 Create StreamStudio web applications. See Deploying web applications on page 66.

14 Create Task Schedulers for template synchronization in the application domains linked to StreamStudio. See Creating a Task Scheduler for template synchronization on page 66.

15 Open Composition Center and verify that everything is OK.16 Publish the document definitions.

Running parallel installationsYou can run version SP5 and version 5.6 in parallel on the same Windows machine. You can set up different enterprise repositories for SP5 and 5.6, but you can also use the same enterprise repository for the two versions. By using the same enterprise repository you will be able to perform a rolling upgrade from SP5 to 5.6.See the Installation Guide for more information about parallel installations using the same enterprise repository.


64 Creating a 5.6 environmentUpgrading from Persuasion SP5

Creating a 5.6 environmentOpen Control Center version 5.6 and create a new site. The new site can be connected to the same enterprise repository used in the SP5 environment but it can also be connected to a separate enterprise repository. See Running parallel installations on page 63.When the site is configured you can add the application domains and applications to the site. You can create the application domains manually or use the Transport and Migration feature in Control Center to import and upgrade application domains from the SP5 environment. See Creating application domains in the 5.6 environment on page 64.You must set up a separate folder structure for the upgraded Design Center Projects. The SP5 Design Center Projects should be kept as they are. To upgrade the Design Center Projects you must first pack the SP5 versions and unpack and upgrade the Projects in the new 5.6 folder structure. See Upgrading Design Center Projects on page 68 for information about how to upgrade Design Center Projects.

In this section

• Creating application domains in the 5.6 environment on page 64• Deploying web applications on page 66• Creating a Task Scheduler for template synchronization on page 66• Creating repository connections on page 67

Creating application domains in the 5.6 environmentYou can create the application domains in the 5.6 environment manually, and manually add all applications (StreamServer applications, service gateways, etc.) to each domain. You can also use the Transport and Migration feature in Control Center to import and upgrade SP5 application domains. See Upgrading application domains using Transport and Migration on page 64.

Upgrading application domains using Transport and MigrationYou can export an application domain from SP5 Control Center to a package file, and use the package file to import the application domain to 5.6 Control Center. The export package includes all hosts and applications in the domain (StreamServer applications, service gateway, etc.). The following configuration files for the applications are also included:• iomanager.xml

• logmanager.xml

• parameters.xml

• repositorymanager.xml

In addition to the above, you can export files inside the working directories of the applications to the package file. See Exporting additional files to a package in the Transport and Migration reference guide for more information.When you import the package file to 5.6 Control Center, all hosts and applications in the package file are added to the 5.6 application domain.


Creating a 5.6 environment 65Upgrading from Persuasion SP5

Upgrading Design Center Projects when importing an application domain

When you import you have the option to upgrade all of, or a subset of, the Design Center Projects deployed to the StreamServer applications in the SP5 application domain. All Projects you select to upgrade are automatically deployed to the corresponding StreamServer applications during the import.Note: You cannot use this feature if the Project contains a global Platform shared

by several Projects.

Before you upgrade Design Center Projects this way, you must pack the projects. The reason is that the Design Center upgrading utility needs Design Center packages (*.dcpackage) as input when upgrading Design Center Projects.

To pack an SP5 application domain

1 Open Control Center SP5.2 Right-click the application domain node and select Pack Application

Domain. The Pack Application Domain dialog box opens.3 In Create package file in, specify the path to the package file and click

Export. The package file (name.domain) is created in the path specified.

To import and upgrade an application domain

1 Open Control Center 5.6.2 Create a new application domain.3 Right-click the new application domain and select Import Application

Domain. The Import Application Domain dialog opens.4 In Import file, browse to and select the package file (name.domain).5 Click Import. The Upgrade and Deploy Applications dialog opens.6 Select the check boxes for all StreamServer applications you want to

upgrade the Design Center Projects for and deploy to.7 Select the first Design Center Project to upgrade (click and high-light the

row for the corresponding StreamServer application).8 In Project package, browse to and select the *.dcpackage to upgrade.9 In Destination Project folder, browse to and select the root folder for the

unpacked and upgraded Design Center Project.10 Continue with the rest of the Design Center Projects to upgrade. You must

specify the Project package for each Project but you can keep the same Destination Project folder.

11 Click OK.The Projects for all selected StreamServer applications are upgraded, unpacked and deployed. The Projects are unpacked in separate folders in the Destination Project folder. The Project folders are named <name>, where <name> is the name of the StreamServer application. Each folder contains the following folders and files:

Folder/file Description

dcexport Folder containing the export from the upgraded Project.


66 Creating a 5.6 environmentUpgrading from Persuasion SP5

Deploying web applicationsIf the SP5 environment contains StreamStudio, Ad Hoc and Reviewer or DBQ Tool you must deploy the same web applications in the 5.6 environment and connect them to the appropriate application domains. See the Control Center user guide for information about how to deploy web applications.

Creating a Task Scheduler for template synchronizationBy default, the latest StoryTeller template version in the runtime repository is exported to the web content repository when a StreamStudio user logs in and navigates to the Composition Center landing page. Thereafter synchronization is triggered according to the trigger interval specified in docdef.xml (default is two minutes). Template synchronization stops when the user logs out.To have more control of template synchronization you can create a Task Scheduler task that triggers the synchronization. This task is configured per application domain. We recommend that you use the Task Scheduler as the only trigger for template synchronization, and disable the default synchronization:1 Open the schedulers.properties file in a text editor. For Tomcat, it is

located in:<Tomcat_installation>\webapps\<App>\WEB_INF\spring\properties

2 Edit templatesynch.local.enabled=falseSee Scheduling synchronization of templates in the Control Center user guide for more information.

dctmp Folder containing the upgraded Design Center Project files.

<name>.dcpackage The upgraded Design Center Project package file.

<name>.log Log file.

Folder/file Description


Creating a 5.6 environment 67Upgrading from Persuasion SP5

Creating repository connectionsIf the SP5 environment contains repository connections (Collector archive, Document broker repository or ELS archive) you must create the same connections in the 5.6 environment and connect them to the appropriate application domains. See the Control Center user guide for information about how to create and link repository connections.

Upgrading Collector archives

To be able to use an SP5 Collector archive in 5.6 you must upgrade the Collector archive:1 In Control Center 5.6, right-click the Collector archive node and select

Create Database.2 Select Apply upgrade and click OK.



Upgrading Design Center ProjectsSet up a separate folder structure for the upgraded Design Center Projects. The SP5 Design Center Projects should be kept as they are. To upgrade the Design Center Projects you must first pack the SP5 versions and save the Project packages in the new 5.6 folder structure.How to proceed depends on whether you will upgrade the Projects manually or use the Transport and Migration feature in Control Center to import and upgrade application domains and upgrade and deploy the Design Center Projects at the same time.

To upgrade a Project manually

1 Unpack the Project in the 5.6 environment.2 Check the upgraded Project in Design Center. See Checking an upgraded

Project on page 68.

To upgrade a Project using Transport and Migration

1 Import and upgrade the application domain that contains the StreamServer application running the Project to upgrade. See Upgrading application domains using Transport and Migration on page 64.

2 Check the upgraded Project in Design Center. See Checking an upgraded Project on page 68.

Checking an upgraded ProjectAfter upgrading a Project, you should check the configuration of the upgraded Project in Design Center.

In this section

• Connectors on page 68• Startup arguments on page 69• Script functions on page 69• Document Broker for FastObjects in 64-bit StreamServe on page 70

ConnectorsSome connectors are affected when you upgrade to version 5.6. When you open the upgraded Project in Design Center 5.6, a log message is displayed for each affected connector in the Design Center log.Affected connectors

Connector Comment





Script functions

FTP input and output

FTP input and output connectors are upgraded to a new type of FTP connector that use TCP/IP profiles and authentication profiles to specify host, port, user name and password. If you used variables in any of these fields in the old connectors they will not work in the upgraded Project.

ADO connectors

Not supported in 64-bit StreamServe. Change to JDBC connectors.

MSMQ connectors




Lotus Notes connector




Connector Comment

Function Comment

Execute Timeout set to zero in Execute() script function is not supported in 5.6. If the timeout is set to zero, Execute() will fail and return Error.











Cloning and migrating application domains 71Upgrading from Persuasion SP5

Cloning and migrating application domainsYou can use the Transport and Migration feature in Control Center to clone application domains and to migrate application domains. Cloning means creating a copy of an application domain, e.g. creating a new application domain in the test environment by cloning an application domain in the development environment. Migrating an application domain means deploying changes from one application domain to another, for example from the development environment to the test environment. See the Transport and Migration reference guide for more information about cloning an migrating application domains.


72 Migrating repositoriesUpgrading from Persuasion SP5

Migrating repositoriesUse DBAT version 5.6

Use DBAT version 5.6 when you migrate repositories. This applies to importing data to 5.6 repositories as well as exporting data from SP5 repositories. See the Database Administration Tool user guide for information about how to start DBAT version 5.6 from the Start menu.

In this section

• Migrating security data on page 72• Migrating web content repositories on page 75• Migrating stored Messages on page 80• Migrating document definitions (runtime repository) on page 83• Command line syntax for repository migration on page 87• Listing all published document definitions on page 89

Migrating security dataYou can migrate security data (roles, permissions, etc.) from the SP5 runtime repository to the 5.6 runtime repository. First you export the security data in the SP5 repository to a ZIP file, and then you use the ZIP file to import the security data to the 5.6 runtime repository.

In this section

• Exporting security data using the DBAT GUI on page 72• Importing security data using the DBAT GUI on page 73• Exporting security data from command line on page 73• Importing security data from command line on page 74

Exporting security data using the DBAT GUIFirst you export the security data in the SP5 repository to a ZIP file, and then you use the ZIP file to import the security data to the 5.6 runtime repository (see Importing security data using the DBAT GUI on page 73).

To export security data

1 Start DBAT version 5.6 and connect to the SP5 runtime repository.2 Click the Runtime Repository category button.3 In the Export section, click Browse. A file browser opens.4 Browse to the folder where to store the zip file, enter the file name and click

Export. The export path is displayed in the Export to field.5 In Areas select Security.6 Click Export. The zip file is created in the folder specified.


Migrating repositories 73Upgrading from Persuasion SP5

Importing security data using the DBAT GUIFirst you export the security data in the SP5 repository to a ZIP file (see Exporting security data using the DBAT GUI on page 72), and then you use the ZIP file to import the security data to the 5.6 runtime repository.

Cleaning the repository before importing

If you select to empty the repository before importing, all resources in all areas (Message store, Security, Composer and Composition Center) are removed from the repository before data is imported from the zip file.If there are dependencies to other areas, e.g. Document Broker, all these messages must be processed or removed separately before you import. If you intend to import into a newly created repository, please note that the repository contains default and basic data from start, i.e. it is not empty.

Overwriting resources when importing

• If you select to overwrite existing resources, all rows are imported from the zip file. Existing rows in the repository are replaced by the corresponding rows imported from the zip file.

• If you select not to overwrite existing resources, only new rows are imported from the zip file.

To import security data

1 Start DBAT version 5.6 and connect to the 5.6 runtime repository.2 Click the Runtime Repository category button.3 In the Import section, click Browse. A file browser opens.4 Browse to the zip file to import and click Import. The import path is

displayed in the Import from field.5 Select whether to Empty the repository before importing, and whether to

Overwrite existing matching data.6 Click Import. Data is imported to the repository.

Exporting security data from command lineFirst you export the security data in the SP5 repository to a ZIP file, and then you use the ZIP file to import the security data to the 5.6 runtime repository (see Importing security data from command line on page 74).

Command syntax

See Command line syntax for repository migration on page 87.

Example 1 Exporting security data (MSSQL)

strs-migrate.bat -a Security -d MSSQL -m EXPORT -n strsDataSP5 -o 1433 -p myPwd -s WMF3K55 -u sa -z C:\strs_data\myDb.zip



Example 2 Exporting security data (Oracle)

strs-migrate.bat -a Security -d ORACLE -i abc321 -m EXPORT -n strsDataSP5 -o 1521 -p myPwd -s salma -u sys -z C:\strs_data\myDb.zip

Importing security data from command lineFirst you export the security data in the SP5 repository to a ZIP file (see Exporting security data from command line on page 73), and then you use the ZIP file to import the security data to the 5.6 runtime repository.

Command syntax


Example 3 Importing security data (MSSQL)

strs-migrate.bat -d MSSQL -m IMPORT -n strsData56 -o 1433 -p myPwd -s WMF3K55 -u sa -z C:\strs_data\myDb.zip

Example 4 Importing security data (Oracle)

strs-migrate.bat -d ORACLE -i abc321 -m IMPORT -n strsData56 -o 1521 -p myPwd -s salma -u sys -z C:\strs_data\myDb.zip



Migrating web content repositoriesYou can migrate document definitions and related resources from the SP5 web content repository to the 5.6 web content repository. First you export the document definitions and resources in the SP5 repository to a ZIP file, and then you use the ZIP file to import the document definitions and resources to the 5.6 web content repository.

Recommendations when migrating web content repositories

• In SP5 domain, stop template synchronization (i.e. log out all users from Composition Center) and service gateway before migrating, and start template synchronization and service gateway when migration is completed. If possible, stop the Composition Center application from the Java application server (e.g. Tomcat) instead of stopping the service gateway. You must have web administrator privileges to be able to stop the Composition Center application.

• In 5.6 domain, stop template synchronization (i.e. stop Task Scheduler for template synchronization) before migrating, and start template synchronization when migration is completed.

• Restart the Java application server when the import is completed.

In this section

• Exporting all document definitions using the DBAT GUI on page 75• Exporting a subset of all document definitions using the DBAT GUI on page 76• Importing document definitions using the DBAT GUI on page 76• Exporting all document definitions from command line on page 77• Exporting a subset of all document definitions from command line on page 78• Importing document definitions from command line on page 79

Exporting all document definitions using the DBAT GUIFirst you export all document definitions and resources in the SP5 repository to a ZIP file, and then you use the ZIP file to import the document definitions and resources to the 5.6 web content repository (see Importing document definitions using the DBAT GUI on page 76).

To export document definitions

1 Start DBAT version 5.6 and connect to the SP5 web content repository.2 Click the Web content Repository category button. The Web content

repository view is activated.3 In the Export section, click Browse. A file browser opens.4 Browse to the folder where to store the zip file, enter the file name and click

Export. The export path is displayed in the Export to field.5 Click Export. The zip file is created in the folder you specified.



Exporting a subset of all document definitions using the DBAT GUI

First you export a subset of the document definitions and related resources in the SP5 repository to a ZIP file, and then you use the ZIP file to import the document definitions and resources to the 5.6 web content repository (see Importing document definitions using the DBAT GUI on page 76).

Using the filter

By default, all document definitions are displayed in the Available Document Definitions table. You can use the filter in this view to limit the number of resources displayed. To use the filter, you enter any sequence of characters in the Filter field. Only table items that contain the same sequence of characters are displayed in the table.


1 Start DBAT version 5.6 and connect to the SP5 web content repository.2 Click the Document Definitions category button. The Document definitions

view is activated.3 In the Available Document Definitions list, select the document definitions to

export (use Ctrl + SELECT or SHIFT + SELECT to multi-select items).4 Click >. All selected document definitions are moved to the Selected

Document Definitions list.5 Click Export. A file browser opens.6 Browse to the folder where to store the file, enter the file name and click

Export. The selected document definition and related resources are exported to the zip file.

Importing document definitions using the DBAT GUIFirst you export the document definitions and related resources in the SP5 repository to a ZIP file (see Exporting all document definitions using the DBAT GUI on page 75 and Exporting a subset of all document definitions using the DBAT GUI on page 76), and then you use the ZIP file to import the document definitions and related resources to the 5.6 repository.


If you select to empty the repository before importing, all data is removed from the repository before data is imported from the zip file.

Overwriting data when importing

• If you select to overwrite existing data, all rows are imported from the zip file. Existing rows in the repository are replaced by the corresponding rows imported from the zip file.

• If you select not to overwrite existing data, only new rows are imported from the zip file.



To import document definitions

1 Start DBAT version 5.6 and connect to the 5.6 web content repository.2 Click the Web content Repository category button. The Web content

repository view is activated.3 In the Import section, click Browse. A file browser opens.4 Browse to the zip file to import and click Import. The import path is



Exporting all document definitions from command lineFirst you export all document definitions and resources in the SP5 repository to a ZIP file, and then you use the ZIP file to import the document definitions and resources to the 5.6 web content repository (see Importing document definitions from command line on page 79).

Command syntax


Example 5 Exporting document definitions and related resources (MSSQL)

strs-migrate.bat -d MSSQL -m EXPORT -n strsWebSP5 -o 1433 -p myPwd -s WMF3K55 -u sa -z C:\strs_data\myDb.zip

Example 6 Exporting document definitions and related resources (Oracle)

strs-migrate.bat -d ORACLE -i abc321 -m EXPORT -n strsWebSP5 -o 1521 -p myPwd -s salma -u sys -z C:\strs_data\myDb.zip



Exporting a subset of all document definitions from command line

You can use the -b flag to export a subset of the document definitions in the web content repository. The -b flag takes an xml file as argument, and this xml file defines which document definitions to export. The xml syntax is illustrated by the following example:

You can create the file manually or run list-resources.bat or the UNIX equivalent list-resources.sh to generate the xml file. See Listing all published document definitions on page 89 for more information.Note: You can only run list-resources.bat/list-resources.sh against a

runtime repository. This means the output xml will only contain published document definitions.

Command syntax



strs-migrate.bat -d MSSQL -m EXPORT -n strsWebSP5 -o 1433 -p myPwd -s WMF3K55 -u sa -z C:\strs_data\myDb.zip -b C:\strs_data\ListResources.xml


strs-migrate.bat -d ORACLE -i abc321 -m EXPORT -n strsWebSP5 -o 1521 -p myPwd -s salma -u sys -z C:\strs_data\myDb.zip -b C:\strs_data\ListResources.xml

<?xml version="1.0" encoding="UTF-8" ?>

<exportpackage xmlns="http://schemas.streamserve.com/exportresourcelist/1.0" xmlns:xs="http://www.w3.org/2001/XMLSchema">

<exportinfo/>

<templates>

<template>

<docdef guid="4028C00E-3A6E-9B15-013A-6E9FF4550001"/>

</template>

...

<template>

<docdef guid="4028C00E-3A6E-A888-013A-BC1C8E47000F"/>

</template>

</templates>

</exportpackage>



Importing document definitions from command lineFirst you export the document definitions and related resources in the SP5 repository to a ZIP file (see Exporting all document definitions from command line on page 77 and Exporting a subset of all document definitions from command line on page 78), and then you use the ZIP file to import the document definitions and related resources to the 5.6 repository.

Command syntax


Example 9 Importing document definitions and related resources (MSSQL)

strs-migrate.bat -d MSSQL -m IMPORT -n strsWeb56 -o 1433 -p myPwd -s WMF3K55 -u sa -z C:\strs_data\myDb.zip

Example 10 Importing document definitions and related resources (Oracle)

strs-migrate.bat -d ORACLE -i abc321 -m IMPORT -n strsWeb56 -o 1521 -p myPwd -s salma -u sys -z C:\strs_data\myDb.zip



Migrating stored MessagesYou can migrate stored Messages from the SP5 runtime repository to the 5.6 runtime repository. This migration will also include the security data (users, roles, etc.) and Composition Center resources (document definitions and related resources). First you export the stored Messages in the SP5 repository to a ZIP file, and then you use the ZIP file to import the stored Messages to the 5.6 repository.Note: The Message Store tables must be created in the 5.6 runtime repository to

be able to import stored Messages. These tables are created the first time you start the corresponding StreamServer applications.

Recommendations when migrating stored Messages

• Stop the corresponding 5.6 StreamServer applications before importing data to the 5.6 runtime repository.



In this section

• Exporting stored Messages using the DBAT GUI on page 80• Importing stored Messages using the DBAT GUI on page 81• Exporting stored Messages from command line on page 81• Importing stored Messages from command line on page 82

Exporting stored Messages using the DBAT GUIFirst you export the stored Messages in the SP5 repository to a ZIP file, and then you use the ZIP file to import the stored Messages to the 5.6 runtime repository (see Importing stored Messages using the DBAT GUI on page 81). The recommendation is to process as many stored Messages as possible before the export.

To export stored Messages


Export. The export path is displayed in the Export to field.5 In Areas select Stored messages.6 Click Export. The zip file is created in the folder specified.



Importing stored Messages using the DBAT GUIFirst you export the stored Messages in the SP5 repository to a ZIP file (see Exporting stored Messages using the DBAT GUI on page 80), and then you use the ZIP file to import the stored Messages to the 5.6 runtime repository.


If you select to empty the repository before importing, all resources in all areas (Message store, Security, Composer and Composition Center) are removed from the repository before data is imported from the zip file.If there are dependencies to other areas, e.g. Document Broker, all these messages must be processed or removed separately before you import. If you intend to import into a newly created repository, please note that the repository contains default and basic data from start, i.e. it is not empty.




To import stored Messages




Exporting stored Messages from command lineFirst you export the stored Messages in the SP5 repository to a ZIP file, and then you use the ZIP file to import the stored Messages to the 5.6 repository (see Importing stored Messages from command line on page 82).

Command syntax


Example 11 Exporting stored Messages (MSSQL)

strs-migrate.bat -a MessageStore -d MSSQL -m EXPORT -n strsDataSP5 -o 1433 -p myPwd -s WMF3K55 -u sa -z C:\strs_data\myDb.zip



Example 12 Exporting stored Messages (Oracle)

strs-migrate.bat -a MessageStore -d ORACLE -i abc321 -m EXPORT -n strsDataSP5 -o 1521 -p myPwd -s salma -u sys -z C:\strs_data\myDb.zip

Importing stored Messages from command lineFirst you export the stored Messages in the SP5 repository to a ZIP file (see Exporting stored Messages from command line on page 81), and then you use the ZIP file to import the stored Messages to the 5.6 repository.

Command syntax


Example 13 Importing stored Messages (MSSQL)


Example 14 Importing stored Messages (Oracle)




Migrating document definitions (runtime repository)You can migrate document definitions and related resources from an SP5 runtime repository to a 5.6 runtime repository. This migration will also include the security data (users, roles, etc.). First you export the document definitions and resources in the SP5 repository to a ZIP file, and then you use the ZIP file to import the document definitions and resources to the 5.6 repository.

Recommendations when migrating document definitions



In this section

• Exporting all document definitions using the DBAT GUI on page 83• Exporting a subset of all document definitions using the DBAT GUI on page 84• Importing document definitions using the DBAT GUI on page 84• Exporting all document definitions from command line on page 85• Exporting a subset of all document definitions from command line on page 86• Importing document definitions from command line on page 87

Exporting all document definitions using the DBAT GUIFirst you export all document definitions and resources in the SP5 repository to a ZIP file, and then you use the ZIP file to import the document definitions and resources to the 5.6 repository (see Importing document definitions using the DBAT GUI on page 84).



Export. The export path is displayed in the Export to field.5 In Areas select Composition Center.6 Click Export. The zip file is created in the folder specified.



Exporting a subset of all document definitions using the DBAT GUI

First you export a subset of the document definitions and related resources in the SP5 repository to a ZIP file, and then you use the ZIP file to import the document definitions and resources to the 5.6 repository (see Importing document definitions using the DBAT GUI on page 84).

Using the filter

By default, all document definitions are displayed in the Available Document Definitions table. You can use the filter in this view to limit the number of resources displayed. To use the filter, you enter any sequence of characters in the Filter field. Only table items that contain the same sequence of characters are displayed in the table.


1 Start DBAT version 5.6 and connect to the SP5 runtime repository.2 Click the Document Definitions category button.3 In the Available Document Definitions list, select the document definitions to

export (use Ctrl + SELECT or SHIFT + SELECT to multi-select items).4 Click >. All selected document definitions are moved to the Selected

Document Definitions list.5 Click Export. A file browser opens.6 Browse to the folder where to store the file, enter the file name and click

Export. The selected document definition and related resources are exported to the zip file.

Importing document definitions using the DBAT GUIFirst you export the document definitions and related resources in the SP5 repository to a ZIP file (see Exporting all document definitions using the DBAT GUI on page 83 and Exporting a subset of all document definitions using the DBAT GUI on page 84), and then you use the ZIP file to import the document definitions and related resources to the 5.6 repository.


If you select to empty the repository before importing, all resources in all areas (Message store, Security, Composer and Composition Center) are removed from the repository before data is imported from the zip file.If there are dependencies to other areas, like Message storage and Document Broker, all these messages must be processed or removed separately before import.






To import document definitions




Exporting all document definitions from command lineFirst you export all document definitions and resources in the SP5 repository to a ZIP file, and then you use the ZIP file to import the document definitions and resources to the 5.6 repository (see Importing document definitions from command line on page 87).

Command syntax



strs-migrate.bat -a CompositionCenter -d MSSQL -m EXPORT -n strsDataSP5 -o 1433 -p myPwd -s WMF3K55 -u sa -z C:\strs_data\myDb.zip


strs-migrate.bat -a CompositionCenter -d ORACLE -i abc321 -m EXPORT -n strsDataSP5 -o 1521 -p myPwd -s salma -u sys -z C:\strs_data\myDb.zip



Exporting a subset of all document definitions from command line

You can use the -b flag to export a subset of the document definitions in the runtime repository. The -b flag takes an xml file as argument, and this xml file defines which document definitions to export. The xml syntax is illustrated by the following example:

You can create the file manually or run list-resources.bat or the UNIX equivalent list-resources.sh to generate the xml file. See Listing all published document definitions on page 89 for more information.

Command syntax



strs-migrate.bat -a CompositionCenter -d MSSQL -m EXPORT -n strsDataSP5 -o 1433 -p myPwd -s WMF3K55 -u sa -z C:\strs_data\myDb.zip -b C:\strs_data\ListResources.xml


strs-migrate.bat -a CompositionCenter -d ORACLE -i abc321 -m EXPORT -n strsDataSP5 -o 1521 -p myPwd -s salma -u sys -z C:\strs_data\myDb.zip -b C:\strs_data\ListResources.xml

<?xml version="1.0" encoding="UTF-8" ?>

<exportpackage xmlns="http://schemas.streamserve.com/exportresourcelist/1.0" xmlns:xs="http://www.w3.org/2001/XMLSchema">

<exportinfo/>

<templates>

<template>

<docdef guid="4028C00E-3A6E-9B15-013A-6E9FF4550001"/>

</template>

...

<template>

<docdef guid="4028C00E-3A6E-A888-013A-BC1C8E47000F"/>

</template>

</templates>

</exportpackage>



Importing document definitions from command lineFirst you export the document definitions and related resources in the SP5 repository to a ZIP file (see Exporting all document definitions from command line on page 85 and Exporting a subset of all document definitions from command line on page 86), and then you use the ZIP file to import the document definitions and related resources to the 5.6 repository.

Command syntax


Example 19 Importing document definitions and related resources (MSSQL)


Example 20 Importing document definitions and related resources (Oracle)


Command line syntax for repository migration

Running Database Administration Tool from command line

Database Administration Tool is run using strs-migrate.bat on Windows and strs-migrate.sh on UNIX. This file is located in:<StreamServe_installation>/Applications/Management/5.6.0/bin

Windows syntax

UNIX syntax

strs-migrate.bat [-a <arg>] -d <arg> [-f] [-i <arg>] [-m <arg>] [-n <arg>] [-o <arg>] -p <arg> [-s <arg>]-u <arg> [-y] [-z <arg>] [-b <arg>]

strs-migrate.sh [-a <arg>] -d <arg> [-f] [-i <arg>] [-m <arg>] [-n <arg>] [-o <arg>] -p <arg> [-s <arg>]-u <arg> [-y] [-z <arg>] [-b <arg>]



Flags and arguments

Flag Argument Description

-a <area> Areas in a runtime repository to export. If this parameter is omitted, all areas are included in the export.You can enter one or more of the following areas as argument:• Security – Roles, permissions, etc.• Composer – Resources used in Composer. The Security area is also

included.• CompositionCenter – Resources used in Composition Center. The

Security area is also included.• MessageStore – Stored Messages. The Security and

CompositionCenter areas are also included.Use the following syntax to specify several areas: Security[|Composer][|CompositionCenter]

-d <dbtype> Database vendor. Enter one of the following as argument:• ORACLE

• MSSQL

-f N/A Forces data overwrite when importing data to a runtime repository.

-i <Instance> Database instance to connect to. Enter one of the following as argument:• <InstanceName> for SQL Server.• <SID> for Oracle.

-m <mode> Mode. Enter one of the following as argument:• INSPECT

Inspect repository.• EXPORT

Export repository data to a zip file.• IMPORT

Import repository data from a zip file.• MIGRATE

Import repository data from a zip file (used when migrating data from e.g. test to production environment in 5.6).

-n <schema> Database to connect to. Enter one of the following as argument:• <DatabaseName> for SQL Server.• <SchemaName> for Oracle.

-o <port> Port. Enter the appropriate port number as argument.Default is 1433 for SQL Server and 1521 for Oracle.

-p <password> Database user password. Enter the appropriate password as argument.

-s <hostName> Host of the database. Enter the appropriate host name as argument.Default is localhost.



Listing all published document definitionsYou can run list-resources.bat or the UNIX equivalent list-resources.sh to generate an xml file that includes all document definitions in a runtime repository. list-resources.bat and list-resources.sh are located in:<StreamServe_installation>/Applications/Management/<version>/bin

When you run list-resources.bat/list-resources.sh, you must point out the service gateway of the application domain that contains the runtime repository. You must also specify the path to the output file (document definition xml). The resulting document definition xml includes all document definitions in the runtime repository. You can open this file in an editor and remove all document definitions (<template>...</template>) you want to exclude from the export. Before you use the file in the document definition export you must open it in a web browser to verify it is not corrupt.

Command syntax

list-resources.bat -t <tPath> -o <oPath>

Example

-u <userName> Database user. Enter the appropriate user as argument.Note: The user must have privileges equal to database/schema owner.

-y N/A Suppresses Database Administration Tool from asking for user confirmation. With this option, you can run Database Administration Tool in batch mode on multiple repositories.

-z <path> Specifies a path:• Mode EXPORT: Path to the zip file to export.• Mode IMPORT and MIGRATE: Path to the zip file to import.Enter the path as argument.

-b <path> Used in mode EXPORT to export document definitions from a runtime repository or web content repository to a zip file. The argument is a path to an xml file that defines which document definitions to export.

Flag Argument Description

<tPath> Path to territory.xml for the service gateway in the application domain:<mgwRoot>\applications\<sgw>\wd\territory.xml

<oPath> Path to the output file.

list-resources.bat -t "C:\ManagementGateway\5.6.0\root\applications\SGW2\wd\territory.xml" -o "C:\STRS_misc\ListResources.xml"


