Subject

Modifications

Project Properties

Resource settings and service settings files are automatically created as resources.xml and services.xml files, respectively. These values will be set, by default, in the Resource settings file and the Service settings file fields of the Project Properties Details tab.

Project Properties – Email Tab

An Email resource will be created and attached to the Resource Name field of the Project Properties' Email tab.

Project Folders

The contents of iBOLT V2.5 project folders will be copied into the Magic xpi project folders during migration.

Project Servers

A Server resource is created and attached to the Server Repository's Resource Name field.

Global Variables

The prefix G is added to all global variables and the length of the variable is, therefore, trimmed from 30 to 28.

Model Variables

Model variables have been changed to context variables. The prefix C is added to all context variables and the length of the variable is, therefore, trimmed from 30 to 28.

Flow Variables

The prefix F is added to all flow variables and the length of the variable is, therefore, trimmed from 30 to 28.

Logical Type Variables

Logical type variables are converted to Boolean.

Component Properties

The Error Behavior property has been removed from the Component Properties dialog box, except for Data Mapper database operations as well as SAP Business One components. The behavior of all steps when there is an error will be Exit.
For SAP Business One components, the Error behavior is only related to multiple operations in the XML interface, such as multiple inserts. If there is an error in one of the SAPB1 methods, the error behavior is Exit, as is the case for the rest of the components.

Configuration File Flags

The V2.5 AutoEndI5MapperSession configuration file flag is replaced with the DB Disconnect property in the Database Schema Properties dialog box.

Database Repository

A new database resource will be created in Magic xpi's Resource Repository for every database entry in iBOLT V2.5's Database Repository. The name of this new database resource will be the same as the database's name in the Database Repository.

Flow Errors

The Save Point option was removed from the Error Policy column. Flows with the Save Point option selected, will have their error behavior automatically changed to Restart.

Step – Internal Interface

In the following components, if the Step Interface is defined as Internal, it will be changed to Method:

• Directory Scanner

• Domino

• uniPaaS

• Encryption

• File Archive

• File Splitter

• HTTP

• SAPB1

Step – Method Interface

A resource is created containing the relevant properties, and the step's settings are updated with the newly-created resource. If more than one method requires a new resource, then the step will be split and a new step will be created for each new resource.

Step – XML Interface

A resource is created containing the relevant properties, and the step's settings are updated with the newly-created resource. The component model's XML is upgraded to a new component model XML. Any connections which are not part of the new XML, or which have become part of the newly-created resource, will be deleted. Existing mappings will be changed to comply with the new Data Mapper rules.

Step Settings

Settings fields (resources) will be created according to the step's data.

Trigger

A service is created containing the relevant properties. If necessary, a resource is also created. Finally, the step's settings are updated with the newly-created service.

Error System Variables

In error flows and exception flows, UserBlob, UserString, and UserCode variables are no longer updated with the error information (SQL statement), the error message, and the error code.

Subject

Modifications

eDeveloper Step

An eDeveloper component will be converted to a uniPaaS service. The uniPaaS component is generated in the %currentprojectdir% folder.

There are a number of modifications required to successfully migrate the eDeveloper V2.5 component. For more information, see Migrating eDeveloper Components.

iBOLT Portal Trigger

The iBOLT Portal component is not supported in Magic xpi, and will be removed from the trigger area.

COM Trigger

A service is created and the relevant entries are copied to the service. dll, jar, and XSD files for the service are created in the <Magic xpi>\projects\<project name>\Service\<COM trigger name> folder.

HTTP Trigger

A service is created and the relevant entries are copied to the service. The trigger component's Settings tab is updated with the newly-created service. The Endpoint Name field is updated with the name that this trigger had in iBOLT V2.5. Then, XSD and HTML files are created in the <Magic xpi>\projects\<project name>\Service\<endpoint name> folder for every endpoint of each service.

SAPB1 Trigger

During migration, a service is created in Magic xpi that is based on the iBOLT V2.5 SAPB1 trigger definitions. The converted trigger(s) will be defined by this service.

If you migrate a project containing an SAPB1 trigger component that invokes different flows, the trigger will be split and each flow will have its own trigger.

The trigger's Polling interval in V3 is defined per Service and during migration it is set to the minimal interval defined in the relevant V2.5 trigger rows.

Invoke Flow Service

This step will be split into the Flow Data Service and the Invoke Flow Service. The Flow Data Service step will be added before the Invoke Flow Service, to update UserCode, UserString and UserBlob variables.

Scheduler Service

The following entries were deleted, and will not be copied to the new service:

• Start date

• Define schedule end

• End date

• End time

Data Mapper

In Magic xpi, the Data Mapper enforces mapping rules in the Studio environment. Furthermore, a condition on the mapped destination elements was established, so that in case no value is available in the Source, no element will be created in the Destination. For example, If there is a simple element connection, and no compound element connection exists for that simple connection, then a compound element connection will be created automatically for it. For more information, see the Data Mapper Rules topic. Note that simple root elements are not supported.

In addition, the following changes occur during migration:

• The Create always property is no longer supported

• Database Repository entries will be replaced by newly created database resources.

• Multiple ODS entries will be created to replace multiple selected ODS entries in iBOLT V2.5.

• If a connection is deleted, conditions and expressions will be removed.

• If a database table contained field names with special characters (such as #, ],[ ", and %), iBOLT V2.5 removed the characters automatically and created the field name without them. Magic xpi does not do this, so during migration any connection to such a field is lost.

• During certain scenarios, the Map button is disabled after the migration. In these cases, you need to go the Source/Destination properties and click OK. One scenario is when a required Environment variable is not set in the magic.ini file before migration.

• For projects using the CallPublic function, make sure all parameter ReturnDataTypes are Alpha.

The following flags are not supported in Magic xpi:

• DebugGenMapper

• DebugGenMapperCMPR

Web Services Step

Web Services Client resources are created according to the Web service step that is configured in iBOLT V2.5. A step with mapping configuration based on an iBOLT V2.5 step will be created in Magic xpi. Data Mappers that handle the request XMLs need to be reconfigured with the new schema that are generated during the conversion process.

Components are generated when you select the Build menu and click Build Solution. These components will be created in the <Magic xpi>\projects\<project name>\Resource\<operation name> folder.

File Management

FTP methods are no longer supported in the File Management component. If an FTP method was used in an iBOLT V2.5 project that is being migrated, the following will take place:

• A new FTP resource will be created in the Magic xpi Resource Repository. The iBOLT V2.5 File Management component's FTP methods' properties will be copied to this new resource.

• A new FTP step will be created, containing the newly-defined resource.

• If the FTP methods have different FTP Server details, a new step will be created for every method.

Web Services Trigger

The migration process identifies all of the Web services triggers that relate to a specific service, and collects all operations information (including schemas). The migration process then creates a suitable service in the Service Repository. Data Mappers that handle the response XMLs need to be reconfigured with the new schema that are generated during the conversion process.

The generated trigger is based on the service and on the original Web services trigger definition. It creates the mapping configuration screen in Magic xpi for that trigger. The Web services trigger in V3 works even if an invalid User is sent in a V2.5 IBPrincipal.

When the Deploy Web service box (in the iBOLT 2.5 to 3.0 Migration dialog box) is checked and the Systinet login information is supplied, all Web services (provider) are generated and deployed to Systinet.

Note that the services deployed to Systinet are new services with a different WSDL than the original one, meaning that you will have to change the client applications accordingly. If you want to preserve the iBOLT 2.5 services and original WSDL, use the Magic xpi bridge configurations.

Components are generated when you select the Build menu and click Build Solution. These components will be created in the <Magic xpi>\projects\<project name>\Service\<operation name> folder.

Directory Scanner

FTP methods in destination directories are no longer supported in the Directory Scanner component. This means that:

• The Directory Scanner's LAN to FTP method, available in iBOLT V2.5, will be replaced by the LAN to LAN method in Magic xpi. The Destination Directory Location will be the %currentprojectdir% folder.

A new FTP step containing the Put method, as well as a defined resource, will be created. The Source File Name will be %currentprojectdir%&UserString, as UserString contains the file name.

• The Directory Scanner's FTP to FTP method has been removed from Magic xpi, and has been replaced by the FTP to LAN method. The Destination Directory Location will be the %currentprojectdir% folder.

Two FTP resources will be created if they are different. The first resource will be attached to it. A new FTP step containing the Put method will be created. The Source File Name will be %currentprojectdir%&UserString, as UserString contains the file name. The second resource will be used.

The Return Filename To parameter is updated with Null if no action is performed, for example, if a file is not found. When the migration has been completed, any expressions that check for the existence of files should be changed manually.

Encryption

The IDEA method is not supported in Magic xpi. You have to configure the step manually.

Directory Scanner Trigger

During the migration process, if the Destination Directory Location is FTP, it is changed to LAN and replaced with the %currentprojectdir% folder.

Logical Names Service

This service was removed. It will be replaced with the Flow Data Service.

Non-Supported Components

The iBOLT V 2.5 eDeveloper trigger is not supported in this version. In Magic xpi, you can define a uniPaaS trigger with the Component SDK, using the existing code.

Removed Components

The following components are not supported in Magic xpi:

• Call COM

• FedEx

• iBOLT Portal

• Java

• SAPB1 6.5

• SMS

• UPS

These components will be converted to work through the NOP service when you migrate iBOLT V2.5 projects to Magic xpi. You should convert eDeveloper-based user defined components individually, and add them to your Magic xpi project.