inubit 6.1 Migration Guide

Transcription

1 inubit 6.1 Migration Guide

2 Copyright Bosch Software Innovations GmbH Schöneberger Ufer Berlin Germany Phone: Fax: URL: Bosch Software Innovations GmbH 2013 Legal Provisions The information and data, including URLs and other references on an Internet basis, contained in this documentation may be changed without prior notice. The product documentation was carefully prepared. However, the information contained therein cannot be guaranteed to reflect the properties of inubit. The liability of Bosch Software Innovations GmbH encompasses only the provisions stated in the sales and delivery conditions. The users are responsible for compliance with all applicable copyrights. Regardless of applicability of the respective copyright laws, no portion of this document may be reproduced or transferred for any purpose, regardless of the means or resources used, electronically or automatically, without prior explicit written approval from Bosch Software Innovations GmbH. Bosch Software Innovations GmbH may be the owner of patents, patent applications, trademarks, copyrights or other rights of intellectual property that concern the content of this document. The provision of this document does not grant license rights to these patents, trademarks, copyrights or other intellectual property, unless this was explicitly granted by Bosch Software Innovations GmbH in a written license agreement. Software provided by Bosch Software Innovations GmbH may include software components of other producers. inubit is a registered trademark of Bosch Software Innovations GmbH. All other product and company names listed in this document may be registered trademarks of their respective owners.

3 Overview 3 1 Overview This manual guides you through the process of migrating an inubit BPM-Suite version 5.1 or higher to the latest inubit version. To migrate an inubit BPM-Suite with an older version (< 5.1), you must migrate it first to version 5.3. Updating Your License If you have concluded a maintenance agreement with the Bosch Software Innovations GmbH, you do not need a new license. You can continue using the license of the source system for migrations within a major release (4.x, 5.x or 6.x). Only for using new features which are added to BPM services already licensed by your company, you have to request a new license key. If you want to use new features which are chargeable, please contact your sales contact at Bosch Software Innovations GmbH or send an to insidesales@bosch-si.com to extend your license. Incompatibilities Along with the numerous improvements and innovations of the inubit software, there are a few incompatibilities which are only relevant in particular use cases. Find the complete list of incompatibilities in the inubit user portal at > Software tab > readme.txt. Announcements of Discontinuation Find the complete list of discontinuations in the inubit user portal under > User-Forum tab > readme.txt. Support If you have questions concerning the migration please contact the inubit support: Phone: SupportSystem: 2 Backing up the Source System Before migrating you must back up the static data in the file system (users, workflows, modules, roles, Repository). 1. Stop the Integration Server. 2. Create a complete backup of the following directories by means of your operating system: - is installation directory inubit 6.1: Migration Guide

4 4 Installing and Configuring the inubit Software - Directories containing graphics or Web applications - Application specific directories In order to back up, copy, for example, all directories to a different server or to another partition of the same server. 3. If you have customized start scripts, also back them up (e. g. settings concerning firewall, port number, proxy and caching). 4. Create a backup of the databases in use: - is Monitoring database, is Task database - Liferay database - Repository database 3 Installing and Configuring the inubit Software 1. Install the inubit software into a new directory. 2. Add your license to the inubit software. The inubit license must cover at least the same scope as the source version license. 3. In case you wish to use a different database for inubit Monitoring, inubit Task and for the Repository than the database included in delivery, proceed as follows: a. Set up the database again or set up a new workspace in the database used up to now. You must not delete the existing databases/workspaces on the source system until the migration is completed. b. Replace the inubit Monitoring database, the Task database, and/or the Repository database. Refer to - Managing inubit Databases (inubit Process Engine: Administrator and Developer Guide, chap. 8, p. 119) - Switching the Repository to an Oracle Database (Workbench: User Guide, chap. 19.1, p. 467) If you want to migrate your Liferay portal, please contact the inubit support inubit 6.1: Migration Guide

5 Executing the Migration Script 5 4 Executing the Migration Script When migrating, almost all processes, artifacts and configurations created in the source system are either taken over into the target system or are adjusted there: System configuration For example, Integration Server configuration, custom plug-in configurations, custom libraries, drivers, Repository, certificates in the Key Manager, watch dog processes of the Connection Manager, application profiles, files related to the portal server and settings of the portal server Users For example users, user groups, process roles, diagrams and modules Operating states For example, activity states of workflows and system connectors, process status data (waitings like timeouts, tasks and task list, queued processes, retries), the complete logging and monitoring database as well as current workflow ID The following components are not migrated: Toolset settings and Toolset reports PITR archive Application server startup script Global folder of the Repository Liferay portal server ExtJS extensions directory server/lib directory The following components are migrated only from certain versions onward: Tasks starting with version 5.1 Task lists (layouts) starting with version 5.1 Source systems as of version , or The activity states of workflows in the source system are taken over into the target system when migrating. If necessary, adjust the states according to the requirements of the target system. 2. Ensure that the database drivers used on the source system are available in the <is-installdir>/server/lib/system directory. 3. Stop both the Integration Server of the source system and the inubit Process Engine of the target system. 4. In the target system navigate to <inubit-installdir>/ server/migration/ and call up the migration script migration.bat or.sh. inubit 6.1: Migration Guide

6 6 Migrating Remote Connectors As parameter enter the path to the Integration Server directory of the system to be migrated, for example: C:\Program files\inubit-suite\ \server If the path contains blanks, you must enclose the path in single quotes (under Windows: double quotes), for example: "C:\Program files\inubit-suite\ \server" If you cancel the migration, modifications that have already been carried out on the target system are not rolled back. You can restart the migration later without any further steps. Source systems up to version , or Perform a system backup by means of a Backup Connector. Refer to the Administrator and Developer Guide of the source version. 2. Stop the Integration Server on the source system and the Process Engine on the destination system. 3. Navigate to the <is-installdir>/server/migration/ directory on the destination system and call the migration script migration.bat or migration.sh. Add the path of the system backup file. Example: migration.bat C:\inubit-IS\server\ibis_root\ibis_data\backup\mySystemBackup.zip If the path contains blanks, you must enclose the path in single quotes (under Windows: double quotes), for example: "C:\inubit Suite\ \server" The backup file is written into a default directory. It is overwritten as soon as the Backup Connector is executed. The data already contained in this directory get lost. 5 Migrating Remote Connectors 1. Install the Remote Connectors using the inubit setup. 2. Take over the configuration of the Remote Connectors used until now from the file remote_conf.xml and the start file. 3. De-install the Remote Connectors used until now inubit 6.1: Migration Guide

7 Migrating External Settings 7 6 Migrating External Settings Individual settings of your configuration will not be adopted automatically and they must not be adopted directly from the source system. Assign these settings to the target system manually. Samples for individual system configurations are JBoss configurations, start scripts and customized settings of the portal: Start files including the size of the used JVM heaps (-Xmx) Customizations of the Tomcat or JBoss configuration, for example: - server.xml in <inubit-installdir>/server/jboss/ server/default/deploy/jbossweb-tomcat55.sar - jboss-service.xml in <inubit-installdir>/server/ JBoss/server/default/conf/ - customized servlet mapping in the Tomcat configuration web.xml Changes of the portal server configuration, for example portalext.properties in <inubit-installdir>/server/ Tomcat/webapps/ROOT/WEB-INF/classes Files for configuring Web applications, for example CSS files in <inubit-installdir>/server/ibis_root/conf/form 7 Starting up and Testing the inubit Software After migrating, only those workflows are active which were already active in the source system. In production systems it can be reasonable to put the system into operation stepwise. In order to do so, activate the maintenance mode before starting the inubit Process Engine. 1. Open the file <inubit-installdir>/server/ibis_root/ conf/ibis_config.xml. 2. Add the following element to the <Properties version="4.1"> section: <Property name="servermaintenancemode" type="boolean">true</property> In case the element already exists and has the value false, change the value to true. 3. Save the changes and close the file. 4. Start the inubit Process Engine. 5. Activate the portal server and deploy the portlet archive. 6. Publish the Web services into the new UDDI. inubit 6.1: Migration Guide

8 8 Starting up and Testing the inubit Software 7. Test the workflows and system connections. 8. Check the logging and monitoring information. 9. Test the portal functionalities inubit 6.1: Migration Guide