Вы находитесь на странице: 1из 126

WeDo Technologies 2015 strictly confidential information. All rights reserved.

System
Integrator Tools

May 3, 2016

Month Day Year

Name Surname

surname@wedotechnologies.com

| Page 1

CONTACTS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

BEFORE WE
START,
INTRODUCTIONS

TRAINER NAME
JOB TITLE
+ 000 93965xxxx
+ 000 000 000 000
name.surname
@wedotechnologies.com

May 3, 2016

| Page 2

TRAINING ICONS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

During the training you will have in several slides a upper right corner icon, that will help you
understand what to do:

Pay Attention

Follow me

Hands on

May 3, 2016

| Page 3

Just listen to the narrator

Do it like here in your environment

Do it by yourself

SYSTEM INTEGRATOR TOOLS


Integrator

AGENDA
1. Standalone/Integrated command line tool
WeDo Technologies 2015 strictly confidential information. All rights reserved.

2. Web Scheduler
3. Assited Migration Service - Dev to Tst to Production

AMS Export
AMS Import
AMS Manifest
Migration

4. Export Import Tool


Export Tool
Replace Tool
Import Tool
5. Backup and Restore
Configurations
Database
File System
6. Upgrading Process

May 3, 2016

| Page 5

May 3, 2016

WeDo Technologies 2015 strictly confidential information. All rights reserved.

1. Standalone/
Integrated
command line tool

| Page 6

STANDALONE/ INTEGRATED COMMAND LINE TOOL


WeDo Technologies 2015 strictly confidential information. All rights reserved.

Overview

The integrators have at their disposal several commands to help on their activities.
The command tools are available at two levels:
1)

Sever Level

2)

Instance Level

Note: All legacy commands are out of of this training scope


May 3, 2016

| Page 7

ENCRYPT-TEXT COMMAND
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Server Level

encrypt-text

Name

encrypt-text

Location

<base_directory>/bin
Options

Description

Optional

--help

Prints the help

-s --silent <Boolean>

Silent mode. Only prints the encrypted text.

-t --text <String>

The text to be encrypted

The encrypt-text script is used to obscure the text and ensure privacy.

May 3, 2016

| Page 8

ENCRYPT-TEXT COMMAND - EXAMPLE


WeDo Technologies 2015 strictly confidential information. All rights reserved.

Server Level

Below is an output example for the execution of this operation. > ./encrypt-text -t
Password1
Text encryptor
Copyright (c) 2001-2007 WeDo Soft, All Rights Reserved
WeDo Soft a division of WeDo Consulting
9ADE26D7D93535B95E71B107A4D8B4FCB620BD441B4B7EF51E91F2DAD02360A4

The encrypted type argument can easily be defined, using ConfigMap, with the following
XML code:

May 3, 2016

<encrypted name="ArgumentName">EncryptedValue</encrypted>

| Page 9

AF-RUN-CMD COMMAND
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Server Level

af-run-cmd
Name

af-run-cmd

Location

<base_directory>/bin
Options

Description

--help

Prints the help

--host <String>

The hostname or IP address to connect to (ex.: localhost)

--input <File [Map]>

The executed operations parameter file. The file should be written in XML and follow
the
ParameterMap
structure
as
follows:
<parameter
type="Map">
<parameter
name="flow_run_id"
type="Integer">999</parameter>
</parameter>

--operation <String>

The operation name to execute

--username <String>

The username used to obtain a connection

--password <String>

The password to validate the username

--port <String>

The port number to connect to (ex.: 17930)

--ssl <String>

Use SSL to establish a secure connection

--uri <String>

The context path where the application is listening to

| Page 10

--encrypted <Boolean> Password is encrypted

--force <Boolean>

Force to login the user if an active session already exists.

The af-run-cmd script is used to execute any server operation


May 3, 2016

Optional

AF-RUN-CMD COMMAND - EXAMPLE


WeDo Technologies 2015 strictly confidential information. All rights reserved.

Server Level

Below is an output example for the execution of one operation (GetServerVersion)


./af-run-cmd --username adm --password Password1 --operation GetServerVersion --host
localhost --port 55001 --uri /xdt/

In this case, the executed operation returns the AF framework version.:


AF Run command tool
Copyright (c) WeDo Technologies
All Rights Reserved
Connection
Server: http://localhost:55001/xdt/
User:
adm
Operation
Name:
GetServerVersion
Input:

Result:
Version (String) "WeDo Technologies (c) 2001-2015, Application Server - 3.2.0.195801"

May 3, 2016

| Page 11

AF-RUN-CMD COMMAND
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Instance Level

af-run-cmd
Name

af-run-cmd

Location

<base_directory>/bin
Options

Description

Optional

--help

Prints the help

--host <String>

The hostname or IP address to connect to (ex.: localhost)

--input <File [Map]>

The executed operations parameter file. The file should be written in XML and follow
the
ParameterMap
structure
as
follows:
<parameter
type="Map">
<parameter
name="flow_run_id"
type="Integer">999</parameter>
</parameter>

--operation <String>

The operation name to execute

--username <String>

The username used to obtain a connection

--password <String>

The password to validate the username

--port <String>

The port number to connect to (ex.: 17930)

--ssl <String>

Use SSL to establish a secure connection

--uri <String>

The context path where the application is listening to

--encrypted <Boolean> Password is encrypted

--force <Boolean>

Force to login the user if an active session already exists.

The difference of this af-run-cmd to the one at server level is that this one have the
parameters; host, port and uri as optional, because it uses the host, port and uri that are
configured by default for the instance
May 3, 2016

| Page 12

May 3, 2016

WeDo Technologies 2015 strictly confidential information. All rights reserved.

8. Web Scheduler

| Page 13

AGENDA
WeDo Technologies 2015 strictly confidential information. All rights reserved.

1. Standalone/Integrated command line tool

2. Web Scheduler

May 3, 2016

| Page 14

SCHEDULER CONFIGURATION
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Scheduler Environment

The Scheduler is a very useful tool to configure jobs, in order to run them at a given time.
To access to Schedulers configuration panel, the user must create a new page, named
Configuration Area (Application RAIDRAS Configuration Area).

May 3, 2016

Settings Button

| Page 15

SCHEDULER CONFIGURATION
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Scheduler Environment

Once the Configuration Area page (1) is created, the Scheduler will be available on the
Scheduler Management Category (2).

May 3, 2016

| Page 16

SCHEDULER CONFIGURATION
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Select a Job

To configure the Scheduler, it is fundamental to Select a Job. On the Select Job tab, the
user must configure it, according with the following parameters:

May 3, 2016

Server (1) The Connection Server used to run the Job.

Select a Job to Schedule (2) The selected Job to be executed.


2

| Page 17

SCHEDULER CONFIGURATION
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Select a Job

Recover Past Jobs Executions (3) When enabled, as the name suggests the system recovers
past Jobs Executions, in case the system is not available.

Notifications (4) Job Status Notifications (Finish, Begin, Error).

3
4

May 3, 2016

| Page 18

SCHEDULER CONFIGURATION
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Select a Job

Notifications Subscribers (5) Users which are going to receive the Previously selected
Notifications (4).

Tags (6) Job Labelling.

5
6
May 3, 2016

| Page 19

SCHEDULER CONFIGURATION
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Schedule Time

Once the Job is configured, it is fundamental to set up, the Job Schedule Time. To do so,
the user must fill the parameters, presented next:

May 3, 2016

Start Time (7) Date from which the scheduler can trigger the job execution.

Job Execution Frequency (8) Frequency with which the Job is triggered (Daily, Weekly,
Monthly, Yearly).
7
8

| Page 20

SCHEDULER CONFIGURATION
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Schedule Time

No End Date (9) When enabled, no End Date is defined.

End After (10) Maximum number of times, the scheduler can trigger, the job execution. When
empty, there is no limit.

End by (11) Date from which the scheduler must stop the job execution.

9
10
11
May 3, 2016

| Page 21

SCHEDULER CONFIGURATION
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Job Configurations

On the last Scheduler tab, the user must define the parameters set out below:

May 3, 2016

Engine Type (12) Engines Flow Type (CBPM & BPMN).

Select a Flow (13) The name of the flow to execute.

Parameters (14) Jobs input parameters.

12
13
14

| Page 22

May 3, 2016

WeDo Technologies 2015 strictly confidential information. All rights reserved.

3. Assited

Migration
Service - Dev to
Tst to
Production

| Page 23

AGENDA
WeDo Technologies 2015 strictly confidential information. All rights reserved.

1. Standalone/Integrated command line tool

2. Web Scheduler
3. Assited Migration Service - Dev to Tst to Production

May 3, 2016

AMS Export
AMS Import
AMS Manifest
Migration

| Page 24

AMS - ASSISTED MIGRATION SERVICES


WeDo Technologies 2015 strictly confidential information. All rights reserved.

Overview

AMS is a tool used to assist the user to select, export and import to other environments,
RAID objects that are stored in OMT (Object Management Toolkit)
To access to AMS configuration panel, the user must create a new page, named
Configuration Area (Application RAIDRAS Configuration Area).

May 3, 2016

Settings Button

| Page 25

AMS CONFIGURATION
WeDo Technologies 2015 strictly confidential information. All rights reserved.

AMS Environment

Once the Configuration Area page (1) is created, the AMS will be available on the AMS
Category (2).

May 3, 2016

| Page 26

May 3, 2016

WeDo Technologies 2015 strictly confidential information. All rights reserved.

AMS Export

| Page 27

AMS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Export Objects

To Export Objects the user just have to click on the Export Objects Action

May 3, 2016

| Page 28

AMS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Export Objects

To restrict the number of objects to export, it is possible to apply filters

May 3, 2016

Filter objects by tags

Filter objects by a Manifest


of objects

| Page 29

AMS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Export Objects

To restrict the number of objects to export, it is possible to apply filters

May 3, 2016

Filter objects by tags

Filter objects by a Manifest


of objects

| Page 30

AMS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Export Objects

To restrict the number of objects to export, it is possible to apply filters

May 3, 2016

Filter objects by tags

Filter objects by a Manifest


of objects
Filter objects by object Type

| Page 31

AMS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Export Objects

To restrict the number of objects to export, it is possible to apply filters

Filter objects by tags

Filter objects by a Manifest


of objects
Filter objects by object Type

By default the Baseline


Objects are filtered, if this
option is selected the
Baseline objects will no
longer be filtered
With this option all objects
dependecies will be
included in the list

May 3, 2016

| Page 32

AMS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Export Objects

To restrict the number of objects to export, it is possible to apply filters

May 3, 2016

| Page 33

AMS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Export Objects

A List of object categories will be displayed.

May 3, 2016

| Page 34

AMS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Export Objects

It is possible to select if all objects selected in the category will be included or not in the
export file.
It is possible to select or deselect the object it self from a category of objects.

For instance to select the Generate Cases CBPM flow from the Category
CBPM.FlowObject

It is possible to include in the export all the objects that depends from a particular object,
by selecting the option Include Dependencies

May 3, 2016

| Page 35

AMS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Export Objects

It is possible to check the Restriction Rules for the list of objects to export.

May 3, 2016

| Page 36

AMS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Export Objects

It is possible to check the Restriction Rules for the list of objects to export.

May 3, 2016

| Page 37

AMS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Export Objects

To Export the Data to a file just click on Export button

May 3, 2016

| Page 38

AMS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Export Objects

The final list of objects will be displayed.

May 3, 2016

| Page 39

WeDo Technologies 2015 strictly confidential information. All rights reserved.

TUTORIAL

Export the Raid Objects from RAID :


1. Create a simple mashup
2. Use the AMS Export functionalty to export that mashup

3. Delete the mashup from you system

May 3, 2016

| Page 40

May 3, 2016

WeDo Technologies 2015 strictly confidential information. All rights reserved.

AMS Import

| Page 41

AMS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Import Objects

To import Objects from


another environment the
action Import Objects
must be selected
Then the file with the
exported objects must be
loaded

May 3, 2016

| Page 42

AMS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Import Objects

To import Objects from


another environment the
action Import Objects
must be selected
Then the file with the
exported objects must be
loaded

May 3, 2016

| Page 43

AMS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Import Objects

To import Objects from


another environment the
action Import Objects
must be selected
Then the file with the
exported objects must be
loaded
Click on Load

May 3, 2016

| Page 44

AMS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Import Objects

To import Objects from


another environment the
action Import Objects
must be selected
Then the file with the
exported objects must be
loaded
Click on Load or use files
already loaded

May 3, 2016

| Page 45

AMS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Import Objects

To import Objects from


another environment the
action Import Objects
must be selected
Then the file with the
exported objects must be
loaded
Click on Load or use files
already loaded
The list of objects will be
displayed

May 3, 2016

| Page 46

AMS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Import Objects

To import Objects from


another environment the
action Import Objects
must be selected
Then the file with the
exported objects must be
loaded
Click on Load or use files
already loaded
The list of objects will be
displayed
The import summary will
be displayed

May 3, 2016

| Page 47

IMPORT RAID OBJECTS


WeDo Technologies 2015 strictly confidential information. All rights reserved.

TUTORIAL

1. Import the file created on the tutorial Export RAID Objects.

2. Check the mashup that you previously created.

May 3, 2016

| Page 48

May 3, 2016

WeDo Technologies 2015 strictly confidential information. All rights reserved.

AMS Manifest

| Page 49

AMS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Create Manifest

It is possible to create a list of objects, using the functionality Create Manifest


The filters will be defined

May 3, 2016

| Page 50

AMS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Create Manifest

The user can select the category of objects and/or objects to include in the manifest

May 3, 2016

| Page 51

AMS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Create Manifest

The user can select the category of objects and/or objects to include in the manifest

May 3, 2016

| Page 52

AMS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Create Manifest

The Final List of objects to include in the manifest will be displayed

May 3, 2016

| Page 53

AMS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

List Manifest

It is possible to list all the manifest loaded in RAID by clicking in List Manifest

May 3, 2016

Check If the
Manifest as
the correct
structure

| Page 54

Load
manifests
from a file

Create a new
Manifest

AMS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

List Manifest

It is possible to list all the manifest loaded in RAID by clicking in List Manifest

May 3, 2016

View, edit,
clone,
remove

| Page 55

Refresh
Manifest
dependencies

Start Export
from the
selected
Manifest

AMS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

List Manifest

It is possible to list all the manifest loaded in RAID by clicking in List Manifest

May 3, 2016

View, edit,
clone,
remove

| Page 56

Refresh
Manifest
dependencies

Start Export
from the
selected
Manifest

WeDo Technologies 2015 strictly confidential information. All rights reserved.

AMS

List Manifest

And export objects from a selected Manifest

May 3, 2016
| Page 57

May 3, 2016

WeDo Technologies 2015 strictly confidential information. All rights reserved.

Migration

| Page 58

MIGRATION
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Edit Connections

In some situations the objects to export have connections dependences


Connections are differences from environment to environment. From DEV to TST or from TST
to PRD.
This way:
the connection should be include in the export
Should be included in the import
And must be edit by the user to the environment right parameters

May 3, 2016

| Page 59

WeDo Technologies 2015 strictly confidential information. All rights reserved.

MIGRATION

Edit Connections

May 3, 2016
| Page 60

WeDo Technologies 2015 strictly confidential information. All rights reserved.

MIGRATION

Edit Connections

Select the connection base to edit

May 3, 2016
| Page 61

WeDo Technologies 2015 strictly confidential information. All rights reserved.

MIGRATION

Edit Connections

Edit the connection URL

May 3, 2016
| Page 62

WeDo Technologies 2015 strictly confidential information. All rights reserved.

MIGRATION

Edit Connections

May 3, 2016
| Page 63

MIGRATION
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Edit Connections

Select the connection configuration to edit

May 3, 2016

| Page 64

MIGRATION
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Edit Connections

Edit the Credentials user and password

May 3, 2016

| Page 65

AGENDA
WeDo Technologies 2015 strictly confidential information. All rights reserved.

1. Standalone/Integrated command line tool

2. Web Scheduler

3. Assited Migration Service - Dev to Tst to Production

AMS Export
AMS Import
AMS Manifest
Migration

4. Export Import Tool

May 3, 2016

Export Tool
Replace Tool
Import Tool
| Page 66

May 3, 2016

WeDo Technologies 2015 strictly confidential information. All rights reserved.

4. Export Import
Tool

| Page 67

EXPORT IMPORT TOOL


WeDo Technologies 2015 strictly confidential information. All rights reserved.

Overview

The Export and Import Tools are tools that can be use for different operations:

Backup RAID configurations

Migrate to other environments

Most of the RAID configurations are on OMT (Object Management Toolkit), and to migrate it is
possible to use the AMS (Assisted Migration Services).
But RAID can have extra configurations/data that are not stored in OMT, to migrate that
configurations/data it is necessary to use the Export Import Tool.

May 3, 2016

| Page 68

May 3, 2016

WeDo Technologies 2015 strictly confidential information. All rights reserved.

Export Tool

| Page 69

EXPORT TOOL
To export the configurations is possible to be done in two ways:
Using the Export instance tool

Using the Export tables tool

ADM
Schema

RAID DEV

DAT
Schema

WeDo Technologies 2015 strictly confidential information. All rights reserved.

Overview

Filesystem

May 3, 2016

| Page 70

EXPORT TOOL
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Using the Export instance tool

The export instance tool allows the user to export all database configurations from an
installed server
Exports only the configurations (data) from the product tables

Requires a file specifying which tables and columns must be exported


This file is always provided by the product and installed for each created instance
The file is located in config/export/ExportTables.xml
grants a high level of customization by allowing the use of filters
Usage:

May 3, 2016

<BASE_DIRECTORY>/bin/export-tables
--export-dir=<export-directory>
[ --tables="..." [ --tables="..." ... ] ]
[ --instance-name=<INSTANCE_NAME> ]
[ --user-filters=<user-filters.xml> ]

| Page 71

EXPORT TOOL
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Export instance tool (additional configuration parameters)

Options

Description

Mandatory

-h,--help

Show help.

-d,--export-dir

Directory where exported data will be stored.

-c,--driver-class

JDBC driver class, if other than Oracle.

-r,--database-url

Database JDBC Url, including password. (Ex: jdbc:oracle:thin:[user]/[pass]@[host]:[port]:[sid]). This option


should be used when connecting to a custom database.

-i,--instance-name

Instance name to access to database configurations. This option is used in conjunction with s option. If
this option is omitted, by default App value is used.

-s,--data-source

Data source name used to establish the database connection. This option can only be used in conjunction
with i option.

-q,--quiet

Run in quiet mode.

-k,--keep-empty-tables

Keep export files for empty tables.

-t,--tables-file

File containing definition of tables to export.

-u,--user-filters

File containing additional filters that should be applied.

-nr,--split-data-tables

Exports one table to several files with a fixed number of registers

-th,--number-of-threads

Execute the export using a fixed number of concurrent threads

May 3, 2016

| Page 72

EXPORT IMPORT TOOL


To be more easy to understand the environment migration process using the export import
tool a tutorial will be use to illustrate it:
The tutorial consists on:
Export all the configurations/data from the environment used so far on this training
Shutdown the environment used so far (designated as Development environment)
Startup a new VM with a new environment (designated as Production environment)
Import the configuration/data into the Production environment

ADM
Schema
DAT
Schema

ADM
Schema

| Page 73

Import

Export
Exported Files

Filesystem

May 3, 2016

RAID PRD

RAID DEV

DAT
Schema

WeDo Technologies 2015 strictly confidential information. All rights reserved.

TUTORIAL

Filesystem

EXPORT TOOL
WeDo Technologies 2015 strictly confidential information. All rights reserved.

TUTORIAL

Export the complete instances configuration of RAID


1. Export to the folder /home/demo/export/ the RAID instance
2. Check on the created folder the files contents

3. Copy the complete folder DAT to your local machine

May 3, 2016

| Page 74

EXPORT TOOL
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Using the Export instance tool

Allows the user to export a set of tables


usually used to export tables that does not belongs to the product tables, but could have
been created for business requirements purposes

Usage:

May 3, 2016

<BASE_DIRECTORY>/bin/export-tables
--export-dir=<export-directory>
[ --tables="..." [ --tables="..." ... ] ]
[ --instance-name=<INSTANCE_NAME> ]
[ --user-filters=<user-filters.xml> ]

| Page 75

EXPORT TOOL
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Export tables tool (additional configuration parameters)

Options

Description

-h,--help

Show help.

-d,--export-dir

Directory where exported data will be stored.

-t,--tables

LIKE-pattern to specify the tables to export (Ex.: 'AF_%'). SELECT statements are also accepted, and
should return LIKE-patterns in the first column. If not specified, all available tables are exported. You can
repeat this option to specify several patterns. By default all tables are exported.

Mandatory

-c,--driver-class

JDBC driver class, if other than Oracle.

-r,--database-url

Database JDBC Url, including password. (Ex: jdbc:oracle:thin:[user]/[pass]@[host]:[port]:[sid]). This


option should be used when connecting to a custom database.

-i,--instance-name

Instance name to access to database configurations. This option is used in conjunction with s option. If
this option is omitted, by default App value is used.

-s,--data-source

Data source name used to establish the database connection. This option can only be used in
conjunction with i option.

-u,--user-filters

File containing additional filters that should be applied.

-q,--quiet

Run in quiet mode.

-nr,--split-data-tables

Exports one table to several files with a fixed number of registers

-th,--number-of-threads

Execute the export using a fixed number of concurrent threads

May 3, 2016

| Page 76

EXPORT TABLES TOOL


WeDo Technologies 2015 strictly confidential information. All rights reserved.

TUTORIAL

Export the customized tables from RAID


1. Export to the folder /home/demo/export/DAT all the data from the schema DAT
2. Check on the created folder the files contents

3. Copy the complete folder DAT to your local machine.

May 3, 2016

| Page 77

May 3, 2016

WeDo Technologies 2015 strictly confidential information. All rights reserved.

Export Structure

| Page 78

WeDo Technologies 2015 strictly confidential information. All rights reserved.

EXPORT STRUCTURE

Each export must be placed in its own directory structure, and contains an ExportInfo.xml

A sample of ExportInfo.xml file:

May 3, 2016

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


<parameter type="Map">
<parameter name="Version" type="String">1.3.3.17501</parameter>
<parameter name="Tables" type="Array">
<parameter type="Map">
<parameter name="Name" type="String">AF_T_OBJ_SPEC</parameter>
<parameter name="Filename" type="String">AF_T_OBJ_SPEC.xml</parameter>
</parameter>
<parameter type="Map">
<parameter name="Name" type="String">AF_T_OBJ</parameter>
<parameter name="Filename" type="String">AF_T_OBJ.xml</parameter>
</parameter>
()
</parameter>
</parameter>

| Page 79

WeDo Technologies 2015 strictly confidential information. All rights reserved.

EXPORT STRUCTURE
Each table file consists of a ParameterMap describing the field structure and records to
insert
A sample of AF_T_OBJ_SPEC.xml file:

May 3, 2016

<parameter type="Map">
<parameter name="DeleteRelations" type="Array">
<parameter type="Map">
<parameter name="Fields" type="Array">
<parameter type="String">OBJ_SPEC_UUID</parameter>
</parameter>
<parameter name="Table" type="String">AF_L_OBJ_SPEC_CHILDS</parameter>
</parameter>
()
</parameter>
<parameter name="Fields" type="Array">
<parameter type="Map">
<parameter name="Name" type="String">OBJ_SPEC_UUID</parameter>
<parameter name="Type" type="String">STRING</parameter>
</parameter>
()
</parameter>
<parameter name="PrimaryKey" type="Array">
<parameter type="String">OBJ_SPEC_UUID</parameter>
</parameter>
<parameter name="Records" type="Array">
<parameter type="Array">
<parameter type="String">f6da5444-d890-4ddd-8d20-35d7c41c7666</parameter>
()

| Page 80

EXPORT STRUCTURE
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Table Definition Structure

Under normal usage of export tools, the tables definition is handled automatically and
knowledge of their structure is not required
However, if its need to use/create a custom table definition file, you need to be familiar
with the file structure to use it correctly. Its structure is described below
A sample:

May 3, 2016

<?xml version="1.0"?>
<parameter type="Map">
<parameter name="Tables" type="Array">
<parameter type="Map">
<parameter name="Type" type="String">File</parameter>
<parameter name="Include" type="String">BaseTables-Definition.xml</parameter>
</parameter>
<parameter type="Map">
<parameter name="Type" type="String">Table</parameter>
<parameter name="Name" type="String">EXTRA_TABLE</parameter>
<parameter name="Filename" type="String">EXTRA_TABLE.xml</parameter>
<parameter name="Fields" type="Array"> ... </parameter>
<parameter name="PrimaryKey" type="Array">
<parameter type="String">
(...)
</parameter>
(...)
</parameter>
</parameter>

| Page 81

May 3, 2016

WeDo Technologies 2015 strictly confidential information. All rights reserved.

Filters

| Page 82

WeDo Technologies 2015 strictly confidential information. All rights reserved.

FILTERS
Filter files, may be used in export scripts as user-defined filters in addition to the
preconfigured product export definitions
In order to filter out the data that the user dont need in the export result.
A sample:

May 3, 2016

<?xml version="1.0"?>
<parameter type="Map">
<parameter name="Filters" type="Array">
<parameter type="Map">
<parameter name="Type" type="String">File</parameter>
<parameter name="Include" type="String">BaseExclusions.xml</parameter>
</parameter>
<parameter type="Map">
<parameter name="Type" type="String">Table</parameter>
<parameter name="Name" type="String">IM_R_JOBS</parameter>
<parameter name="PosRestrictions" type="Array">
(...)
</parameter>
</parameter>
</parameter>
| Page 83

WeDo Technologies 2015 strictly confidential information. All rights reserved.

FILTERS
Each of the entries in
PreRestrictions,
Restrictions or

PosRestrictions
is a ParameterMap of one of four types depending on the Type parameter.

Include
Exclude
IncludeFK

ExcludeFK

May 3, 2016

| Page 84

WeDo Technologies 2015 strictly confidential information. All rights reserved.

FILTERS
Include Sample

Exclude Sample

May 3, 2016

| Page 85

<parameter type="Map">
<parameter name="Type" type="String">Include</parameter>
<parameter name="Filter" type="Array">
<parameter type="Map">
<parameter name="Name" type="String">FLOW_NAME</parameter>
<parameter name="Match" type="String">Equal</parameter>
<parameter name="Value" type="String">Flow 3</parameter>
</parameter>
<parameter type="Map">
<parameter name="Name" type="String">FLOW_VERSION</parameter>
<parameter name="Match" type="String">Equal</parameter>
<parameter name="Value" type="String">1</parameter>
</parameter>
</parameter>
</parameter>

<parameter type="Map">
<parameter name="Type" type="String">Exclude</parameter>
<parameter name="Filter" type="Array"/>
</parameter>

FILTERS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

IncludeFK and ExcludeFK

These filters perform matching on each record based on the existence or not of a related
record in another previously exported table.
Records that match this validation are either explicitly included or excluded from the
If a table being extracted contains FK filters referencing another table not yet exported, that
table is exported before the current one continues.
An error only occurs if circular dependencies are found.

May 3, 2016

| Page 86

FILTERS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

IncludeFK and ExcludeFK

IncludeFK Sample
<parameter type="Map">
<parameter name="Type" type="String">IncludeFK</parameter>
<parameter name="RemoteTable" type="String">BPM_T_FLOWS</parameter>
<parameter name="FKFields" type="Array">
<parameter type="Map">
<parameter name="LocalName" type="String">BPM_FLOW_ID</parameter>
<parameter name="RemoteName" type="String">FLOW_ID</parameter>
</parameter>
</parameter>
</parameter>

ExcludeFK Sample

May 3, 2016

<parameter type="Map">
<parameter name="Type" type="String">ExcludeFK</parameter>
<parameter name="RemoteTable" type="String">BPM_T_FLOWS</parameter>
<parameter name="Present" type="Boolean">False</parameter>
<parameter name="FKFields" type="Array">
<parameter type="Map">
<parameter name="LocalName" type="String">BPM_FLOW_ID</parameter>
<parameter name="RemoteName" type="String">FLOW_ID</parameter>
</parameter>
</parameter>
</parameter>
| Page 87

FILTERS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Samples

Several sample file filters are provided with product installation in


the following directory:
<Product Base Dir>/software/components/raid/config/export/filter-samples

May 3, 2016

| Page 88

EXPORT TABLES TOOL


WeDo Technologies 2015 strictly confidential information. All rights reserved.

TUTORIAL

Export the customized tables from RAID and CM with some filters:
1. Export to the folder /home/demo/export/FILTER all the data from the schema ADM with
the follow filters
2. Sequence (AF_T_NUMERIC_SEQUENCE ), must not begin with a SEQ_RV (not like
SEQ_RV%)
3. Include all records from BCM_T_ENT and all its foreign keys to BCM_T_ATT
4. Exclude all the records on AF_T_EVENT
5. Copy the complete folder DAT to your local machine.

May 3, 2016

| Page 89

May 3, 2016

WeDo Technologies 2015 strictly confidential information. All rights reserved.

Replace Tool

| Page 90

REPLACE TOOL
WeDo Technologies 2015 strictly confidential information. All rights reserved.

IncludeFK and ExcludeFK

The next set of slides will describe the replacement tool bundled with the product that can be
used to update selected tokens in database entries, configuration files, export files, etc.
The tool requires two files for execution:
A definition

file

A configuration

file

The definition file template is parsed and placeholders are replaced by the actual values. The
replacement actions are then executed.

May 3, 2016

| Page 91

WeDo Technologies 2015 strictly confidential information. All rights reserved.

REPLACE TOOL

Usage:
Invocation:
<PRODUCT BASE DIR>/bin/replace-tool
--definition=<def-file.template>
[ --instance-name=<instance name> ]
[ --config-file=<config-file> ]
[ --props=<properties-file> ]

Sample

May 3, 2016

usage:
bin/replace-tool
--definition=software/components/raid/config/replace/update-export.xml.template
--instance-name=RAID

| Page 92

REPLACE TOOL
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Replace tables tool (additional configuration parameters)

Options
-h,--help

Show help.

-d,--definition

A file with the definition of fields to update.

-c,--config-file

Uses a configuration file to specify the values to replace. When used with -n
option, the configuration values are merged.
Note: This is not the same config file used to install the server, this is a new
file to replace values.
Use the instance configuration values to specify the values to replace.

-n,--instance-name
-p,--props

May 3, 2016

| Page 93

Description

Uses a property file to specify the values to replace. When used with -n or -c
options,
the
configuration
values
are
merged.
(See
http://en.wikipedia.org/wiki/.properties)

Mandatory

REPLACE TOOL
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Replace tables tool (additional configuration parameters)

The replacement actions to perform are configured in the definition file using XML syntax.
The top-level element must be domains, containing one or more domain elements, as in the
following example:

May 3, 2016

<?xml version="1.0"?>
<domains>
<domain class="..." ...>
<action class="..." .../>
<action class="..." ...>
...
</action>
...
</domain>
<domain class="..." ...>
...
</domain>
...
</domains>

| Page 94

REPLACE TOOL
WeDo Technologies 2015 strictly confidential information. All rights reserved.

File Structure Definition

Each domain element must contain at least a class attribute


Each domain must have one or more action elements (replacements to be made, etc)
Each action requires at least the class attribute

Note: The definition file is a template file that is processed to replace variable placeholders
and produce the final definition file. For this reason, some characters such as $ must be
properly escaped in order to reach the final replacement configuration. To escape this
character you need to add the underscore character following the $, e.g. $text must be
escaped as $_text

May 3, 2016

| Page 95

REPLACE TOOL
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Domain Types - Database

This domain type fetches and updates values from a column in a table. The records to update
can be restricted by filters.
This supports using the same set of replacement actions for more than one column (on the
same or different tables).
Sample configuration:

May 3, 2016

<!-- Database update example -->


<domain class="wedo.ie.domains.Database"
url="$RAID_DB_APP_URL" driver="oracle.jdbc.driver.OracleDriver"
user="$RAID_DB_APP_USER" pwd="$RAID_DB_APP_PASSWORD">
<table name="BPM_T_FLOWS" field="FLOW_DEFINITION">
<record>
<field name="STATUS">3</field>
</record>
</table>
<action class="wedo.ie.actions.XmlUpdate">
<!-- Update SqlTask passwords -->
<elementtext xpath="//parameter[@name='password']">
<action class="wedo.ie.actions.StringSet" value="${RAID_DB_APP_PASSWORD}"/>
</elementtext>
</action>
</domain>
| Page 96

REPLACE TOOL
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Domain Types

The database domain has the following attributes:


Attribute

Description

Class

Always wedo.ie.domains.Database.

Driver

url

Java
class
implementing
the
database
JDBC
driver.
Example:
oracle.jdbc.driver.OracleDriver
JDBC url for the database to connect to. Example: jdbc:oracle:thin:@[host]:[port]:[sid]

user

Database user name

pwd

Database password

Mandatory

Apart from the attributes, this domain also requires one or more table child elements,
specifying which tables, columns and records to update.
The attributes for the table child element are:
Attribute

Description

Name

Name of the table to updatea

field

Name of the column to update

Method

If EXCLUDE_LIST is specified, the restriction definitions are considered as the


records NOT to update, otherwise the restrictions select only the records to update.

Mandatory

Default is
Empty

May 3, 2016

| Page 97

REPLACE TOOL
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Domain Types

Finally, each table element can have one or more record elements, which define one or more
child field values for the restrictions (refer to the last example for the correct syntax). If there
arent anyrecordelements, all records are updated (or none if EXCLUDE_LIST is used).
Siblings of the table elements (child of the domain) can exit one or more action elements
describing the replacements to be applied.

May 3, 2016

| Page 98

REPLACE TOOL
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Domain Types File System

This domain type fetches and updates the contents of text files in a directory. Multiple files can
be selected by supplying a wildcard file pattern.
Nested in the domain element are one or more action elements describing the replacements
to be applied.
Sample configuration:
<!-- Filesystem update example -->
<domain class="wedo.ie.domains.Filesystem" mask="BCM_*.xml" path=".">
<action class="..." .../>
...
</domain>

The filesystem domain has the following attributes:


class

Attribute

Description
Always wedo.ie.domains.Filesystem

path

Absolute or relative path containing the files to modify

mask

DOS-like mask for filenames to be modified. Examples: *.xml, Flow_*.xml, afinstance.conf,

encoding

May 3, 2016

| Page 99

Note: The file mask is case-sensitive.


A java charset name, for converting the files bytes to characters, and vice-versa
when writing the modified values back to file. Examples: UTF-8, ISO-8859-1, ISO8859-2, etc.

Mandatory

Default is
Empty

REPLACE TOOL
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Action Types - String Replace

This action replaces all occurrences of a chars sequence with a new value. The search
operation is case-sensitive.
Sample configuration:
<!-- StringReplace example -->
<action class="wedo.ie.actions.StringReplace" toReplace="FALSE" newChars="TRUE"
encrypt="false" />

The filesystem domain has the following attributes:

May 3, 2016

Attributea

| Page 100

class

Description
Always wedo.ie.actions.StringReplace

toReplace

Value being searched in the received contents. The matching is case-sensitive.

newChars

New value to replace every occurrence of the previous value (can be empty).

encrypt

If true, the content of newChars attribute are encrypted. This is useful when a
password is stored. If not present the default value is false.

Mandatory

REPLACE TOOL
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Action Types - String Set

String Set unconditionally sets the received contents to the configured fixed value.
This action should typically be applied when receiving specific contents, not to the full
contents of files or Xml Clobs. It is normally nested inside the XmlUpdate action (see below).

Sample configuration:
<!-- StringSet example -->
<action class="wedo.ie.actions.StringSet" value="RAID" encrypt="false" />

The element for this action has the following attributes:

May 3, 2016

Attribute

| Page 101

Description

class

Always wedo.ie.actions.StringSet

value

New value for the received contents (can be empty).

encrypt

If true, the content of the value attribute is encrypted. This is useful when a
password is stored. If not present the default value is false.

Mandatory

REPLACE TOOL
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Action Types - Regular Expression Replace

Replaces all occurrences of regular expressions with a new value.


Sample configuration:
<!-- RegExpReplace example -->
<action class="wedo.ie.actions.RegExpReplace" toReplace="^DAT$" newChars="Data"/>

The element for this action has the following attributes:

May 3, 2016

Attribute
class

toReplace
newChars

| Page 102

Description
Always wedo.ie.actions.RegExpReplace

Regular expression being searched in the received contents. The matching is


case-sensitive unless the (i?) flag is specified.
New value to replace every occurrence of the previous value. It can be empty,
and can also use the values from capturing groups using the $n syntax.

Mandatory

REPLACE TOOL
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Action Types - Regular Expression Replace

The regular expression uses Java-like syntax. The following table shows several examples for
typical replacement scenarios:
toReplace

Description

Original value

Replaced value

DAT
START_DATE
DaT
DAT

Data
START_DataE
DaT
Data

START_DATE

START_DATE

DaT

Data

# comment #

// comment

# multi-line

# multi-line

comment #

comment #

# multi-line

// multi-line

comment #

comment

A=1

A := 1

C>5

C>5

B=2

B := 2

DAT

Data

Replaces any occurrence of DAT by Data, including in the middle of the


contents.

^DAT$

Data

Replaces the full string DAT by Data. Does not replace partial contents,
the full original value must be DAT.

(?i)DAT

^#(.*)#$

(?s)^#(.*)#$

(?m)^(.*)=(.*)$

May 3, 2016

newChars

| Page 103

Data

//$1

//$1

$1 := $2

The (?i) flag activates case-insensitive matching.

Replaces contents starting and ending with # with the same contents
prefixed with // (capturing group 1).

The (?s) activates single-line mode. LF and CR are considered as


any other character, in a single line.

The (?m) activates multi-line mode. Each line is processed


independently.

REPLACE TOOL
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Action Types - XML Update

This action parses the received contents as XML, selects elements using XPath notation and
applies child actions to the elements text contents.
Sample configuration:
<!-- XmlUpdate example -->
<action class="wedo.ie.actions.XmlUpdate">
<elementtext xpath="/flow/flowsharedarea/parameter[@name='ContextType']">
<action .../>
...
</elementtext>
<deletenode xpath="/flow/flowsharedarea/parameter[@name='ContextType']">

<attributetext xpath="/flow/flowsharedarea/parameter/@name">
<action .../>
...
</attributetext>
...
</action>

The element for this action has the following attributes:


Attribute
class
May 3, 2016

| Page 104

Description
Always wedo.ie.actions.XmlUpdate

Mandatory

REPLACE TOOL
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Action Types - Inner Actions

The following table describes the nested actions that can be used in the XmlUpdate action.

May 3, 2016

Sub Actions

Description

Attributes

Name
elementtext

deletenode

attributetext

| Page 105

Mandatory

Description

The XPath
expression for
selecting the
elements to
update

This action selects the text content inside of each element that
matches the XPath expression. The text can be manipulated by
one or more nested action elements.
Deletes all the nodes that match the XPath expression.a

xpath
This action selects the text content of each attribute that
matches the XPath expression. The text can be manipulated by
one or more nested action elements.

REPLACE TOOL
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Action Types - Inner Actions

Some sample XPath expressions are shown below:

May 3, 2016

XPath expression
/flow/flowsharedarea/parameter[@name='ContextType']

Description
Selects a flow root element, then any flowsharedarea
children, and finally parameter children containing the
attribute name with the value ContextType.
Replacement actions are performed on the text
contents of the selected parameter elements.

/flow/tasklist/*[(name()='task'
or
name()='starttask'
or Performs replaces on the contents of
name()='endtask') and @taskkey='TaskSql']/parameter[@name='user']
parameter elements with the name attribute

with the value user, contained inside task,


starttask or endtask elements of the tasklist
element.
/parameter/parameter[@name='Records']/parameter/parameter[position( Selects the value of the INSTANCE_ID field of each
)=count(/parameter/parameter[@name='Fields']/parameter/parameter[@n record, in the layout used by the Import/Export tool.
ame='Name' and text()='INSTANCE_ID']/../preceding-sibling::*)+1 and
count(/parameter/parameter[@name='Fields']/parameter/parameter[@nam
e='Name' and text()='INSTANCE_ID'])=1]

| Page 106

REPLACE TOOL
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Sample

In the installation you can find some sample definition files that can
help you to produce your own definition file. These files are located
under the following directory:
<Product Base Dir>/software/components/ie/config/samples/replace

May 3, 2016

| Page 107

EXPORT TABLES TOOL


WeDo Technologies 2015 strictly confidential information. All rights reserved.

TUTORIAL

Replace the name of the server, for


Replace the name of the tablespace used for some of the tables on the BCM_T_ENT table

May 3, 2016

| Page 108

May 3, 2016

WeDo Technologies 2015 strictly confidential information. All rights reserved.

Import Tool

| Page 109

WeDo Technologies 2015 strictly confidential information. All rights reserved.

IMPORT TOOL
The import tool allows you to upload all data stored in an export. This tool reads all data from
the export directory and uploads it into the database.
By default, the import tool uses insertions to perform this task but updates can be used if you
enable an option in the tool.
This tool guarantees that all data is imported correctly, or none is imported if any error
occurred during the import process.
This mechanism ensures that no partial information is uploaded and leaves the server
database inconsistent.

May 3, 2016

| Page 110

IMPORT TOOL
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Using the Import Tool

Usage:
This example imports all configurations from an export. The update-data option can be
used to allow updates when the records already exist, and to insert new ones.
Invocation:
<PRODUCT BASE DIR>/bin/import
--import-dir=<export-directory>
--instance-name=<instance name>
[ --update-data ]

Sample

May 3, 2016

usage:
bin/import
--import-dir=exports/BC
--instance-name=BC
--update-data

| Page 111

IMPORT TOOL
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Import tool (additional configuration parameters)

The following table provides additional options for the command.


Options
-h,--help

Show help.

-d,--import-dir

Directory with the exported files to be imported.

-c,--driver-class

JDBC driver class, if other than Oracle.

-r,--database-url

Database
JDBC
Url,
including
password.
(Ex:
jdbc:oracle:thin:[user]/[pass]@[host]:[port]:[sid]). This option should be used when
connecting to a custom database.
Instance name to access database configurations. This option is used in conjunction with
s option. If this option is omitted, by default App value is used.

-i,--instance-name

-s,--data-source

Mandatory

-u,--update-data

Data source name used to establish the database connection. This option can
only be used in conjunction with i option.
Update existing records and only insert new ones.

-q,--quiet

Run in quiet mode.

May 3, 2016

| Page 112

IMPORT TOOL
WeDo Technologies 2015 strictly confidential information. All rights reserved.

TUTORIAL

Transfer the export previously extrecated to a new Virtual Machine.


1. Get the extracted data to your local machine from:

/home/demo/export/TUTORIAL2
2. Prepare a new environment
3. Transfer the extracted data to the new environment and import the data to the new
envirnoment.

May 3, 2016

| Page 113

AGENDA
WeDo Technologies 2015 strictly confidential information. All rights reserved.

1. Standalone/Integrated command line tool


2. Web Scheduler
3. Assited Migration Service - Dev to Tst to Production

AMS Export
AMS Import
AMS Manifest
Migration

4. Export Import Tool


Export Tool
Replace Tool
Import Tool
5. Backup and Restore

May 3, 2016

Configurations
Database
File System
| Page 114

May 3, 2016

WeDo Technologies 2015 strictly confidential information. All rights reserved.

5. Backup and
Restore

| Page 115

BACKUP AND RESTORE

WeDo Technologies 2015 strictly confidential information. All rights reserved.

Configurations

To backup the RAID configurations


All

Instances should be shutdown.

Export

all the configurations from all the instances

To restore the RAID configurations


All

instances shoule be shutdown

Import

May 3, 2016

all the configurations to all the instances (with update option)

| Page 116

BACKUP AND RESTORE

WeDo Technologies 2015 strictly confidential information. All rights reserved.

Database and Filesystem

To backup the Database data


Make

a full export for the data schema on RAID DAT schema user

To restore the Database configurations


Import

the result of the export

By default there are no files need to be copy or save on RAID, but dependes on the way the
process are created on RAID it would be necessary to save some files, set of files, or even
folders.

May 3, 2016

| Page 117

AGENDA
1. Standalone/Integrated command line tool
WeDo Technologies 2015 strictly confidential information. All rights reserved.

2. Web Scheduler
3. Assited Migration Service - Dev to Tst to Production

AMS Export
AMS Import
AMS Manifest
Migration

4. Export Import Tool


Export Tool
Replace Tool
Import Tool
5. Backup and Restore
Configurations
Database
File System
6. Upgrading Process

May 3, 2016

| Page 118

May 3, 2016

WeDo Technologies 2015 strictly confidential information. All rights reserved.

6. Upgrading
Process

| Page 119

UPGRADE PROCESS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Overview

The following slides will shows all the necessary actions to execute in order to successfully
upgrade a server.
The

first step is to stop all instances in the server

Create

a database backup for all instances created under the <RAID PRODUCT BASE
DIR> location.

Create

a backup of the <RAID PRODUCT BASE DIR>.

Remove

the existence of patches.


Location:<RAID PRODUCT BASE DIR>/instances/<Instance Name>/patch

May 3, 2016

| Page 120

UPGRADE PROCESS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Overview
Deploy

the new software version in the same location of the existing RAID location.
java jar <RAID package name>.jar u o <RAID PRODUCT BASE DIR>

If

any of the instances have add-ons installed, is necessary to upgrade all of them to the
version that is compatible with this RAID version.
To upgrade an add-on, is necessary to deploy its new software version using the following
command
<RAID PRODUCT BASE DIR>/bin/addon-software-update p <addon package name>.jar

An

instance update that need additional configuration parameters. It is necessary to


generate a new configuration file using the following command:
<RAID PRODUCT BASE DIR>bin/config-generator t <instance type> -o <output-file>

Upgrade

all instances installed under the <RAID PRODUCT BASE DIR>. For each instance,
execute the following command:

May 3, 2016

| Page 121

UPGRADE PROCESS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Overview
Upgrade

all instances installed under the <RAID PRODUCT BASE DIR>. For all instance,
the following command is needed to be executed
<RAID PRODUCT BASE DIR>/bin/update-instance n <instance name> -l <license file>

Start

all instances of RAID server.

Check

May 3, 2016

if the server is working properly. If so, all patches and backups can be deleted

| Page 122

UPGRADE PROCESS
WeDo Technologies 2015 strictly confidential information. All rights reserved.

Final Note
In

some situations to upgrade the server is necessary to use the tools that you have learn in
this training chapter
Assiste Migration Service
Export Import Tool
Upgrade

This way, you need to use the tools at your disposal properly.

May 3, 2016

| Page 123

AGENDA
1. Standalone/Integrated command line tool
WeDo Technologies 2015 strictly confidential information. All rights reserved.

2. Web Scheduler
3. Assited Migration Service - Dev to Tst to Production

AMS Export
AMS Import
AMS Manifest
Migration

4. Export Import Tool


Export Tool
Replace Tool
Import Tool
5. Backup and Restore
Configurations
Database
File System
6. Upgrading Process

May 3, 2016

| Page 124

May 3, 2016

WeDo Technologies 2015 strictly confidential information. All rights reserved.

Q&A

| Page 125

May 3, 2016
| Page 126

WeDo Technologies 2015 strictly confidential information. All rights reserved.

Вам также может понравиться