What's Different in Magic xpi 4.5 (Magic xpi 4.5)

New Features

• A Visual Studio-based workspace with docking capabilities.

• The Data Mapper can now work with JSON schemas.

• In addition to the existing MAGIC_SPACE, Magic xpi now includes a MAGIC_INFO space that holds the Activity Log as well as statistics for the monitor and ODS data. An MGMirror processing unit was also added, which is responsible for managing the write operation of the Activity Log and ODS data to the database.

• A MiniMap to enable you to navigate quickly within long or wide flows.

• A Flow Enablement service. Now the flow enablement can be defined as an external service and can be modified and affect a project without the need to rebuild the project.

• A Scheduler service. Now the scheduler can be defined as an external service and can be modified and affect a project without the need to rebuild the project.

• A Dynamics AX 2012 connector is now offered as a built-in connector in Magic xpi 4.5.

• An MQTT connector is now offered as a built-in connector in Magic xpi 4.5. This connector lets you work with MQ Telemetry Transport (MQTT), a lightweight network protocol used for publish-subscribe messaging between devices.

• A WCF Client connector is now offered as a built-in connector in Magic xpi 4.5. This connector generates C# code to access .dll files and schemas for later use during runtime. It provides easy and secure access and consumption to a large library of services based on this worldwide standard.

• Salesforce licensing prerequisites. To be able to use a Magic xpi license for Salesforce, you now have to install the Magic xpi monitoring app from the Salesforce AppExchange. For information about how to do this, see the How Do I Install the Magic xpi Salesforce App? topic. (Since version: 4.5a)

• Salesforce monitoring utility. You can monitor your Magic xpi environments, view running projects, receive alerts, and get chatter notification about various events using the Magic xpi Force.com monitoring utility. For information about how to do this, see the How Can I Monitor My Project Using Salesforce? topic. (Since version: 4.5a)

• Java 8.0 support. Magic xpi was tested and is compatible to work with JRE 8.0. Note that JRE 8.0 is not supported for Systinet-based Web services (both consumer and provider). For the Windows operating system, to use a Web service consumer, you can use the WCF client. (Since version: 4.5a)

• SAP S/4 HANA support. Magic xpi was tested and is compatible to work with the SAP S/4 HANA platform. (Since version: 4.5a)

Enhancements

• SDK: The enhanced SDK, now known as the Connector Builder, lets you build, distribute and sell professional looking connectors. This version lets you build dynamic steps and triggers. For an in-depth explanation of how to use the Connector Builder, see the Magic xpi Connector Builder PDF in the Magic xpi installation.

• Debugger: The Breakpoints and Suspends pane is now accessible during development.

• The Dynamics CRM connector supports additional authentication types. It is now a .NET connector for on-premise Dynamics CRM servers and not a Java connector as in previous versions. For online servers, it is still a Java connector. Note: When you set the Dynamics CRM resource's Secured Connection property to Yes and the Deployment Type to On Premise, set the DCRMAD flag in the Magic.ini file's [MAGIC_IBOLT] section to Y.

• The enhanced Google Drive connector enables Magic xpi to handle any kind of document used by Google Drive™.

• The SFTP network protocol is now supported.

• The Monitor's Space alert definitions and thresholds are now loaded from: Runtime\Gigaspaces\config\alerts\alerts.xml.

• The Debugger's timeout settings can now be easily accessed so that the Debugger can be configured to work in an optimal way with a particular project.

• In the Monitor's Messages window, the Messages History Export button lets you generate a CSV file containing all the messages in a particular project.

• You can now filter the Monitor's Activity Log messages when working offline.

• The Magic Monitor lets you force the immediate invocation of a Scheduler on a specific flow, without changing the next trigger invocation time, once the project is running again. You do this by selecting Invoke from the Scheduler's context menu.

• Magic xpi was tested and is compatible to work with Windows® 10.

• You can now determine which database schema will be loaded by default from the cache (offline) and which will attempt to connect to the database in order to refresh its structure (online).

• You can refresh multiple database schemas by clicking the button on the toolbar or by clicking the Edit menu and selecting Refresh Database Schemas.

• You can now use Magic xpa user-defined functions in Magic xpi.

• Magic xpi is now using a dedicated class loader for loading all of the JD Edwards Enterprise One jar files. It is no longer necessary to specify these jar files in the classpath (either the machine classpath or the Magic.ini classpath) and no longer necessary to copy them to the Magic xpi folder. The JDE connector now has a dedicated folder for all of its jar files.

• When using the Java Class connector, the Studio no longer loads the Magic.ini file's classpath. Instead, you need to list the jar files in the machine's classpath or copy the jar files to the runtime\java\lib folder.

• Return Description is now available as an output element of the WebSphere MQ trigger.

Studio Changes

Magic xpi is now based on Visual Studio, and includes:

• A Toolbox pane that replaces the Components pane. All the Magic xpi components and utilities appear in this pane, grouped together under specific categories.

• A Solution Explorer that replaces the Navigation pane.

• A dedicated Properties pane that displays the properties of whichever part of the project that you are parked on.

• A Settings dialog box that includes the Resource Repository, Service Repository, and IFS Settings dialog box from Magic xpi 4.1. This also includes the Magic.ini file settings. This can also be accessed as a stand alone editor, allowing you to configure your project without actually opening the Magic xpi Studio.

• The Magic Monitor now includes support for the Activity Log, ODS, and BAM.

• A combined search functionality. The Find Name and Text Search of Magic xpi 4.1 were combined into the Find Text dialog box.

• The copy and paste mechanism has been enhanced, including the support of multiple pasting of steps and branches.

• Non-English characters can be used in the names of business processes, flows, and steps, as well as in descriptions. The names of projects, resources, services and variables can only be written in English characters or the language of your machine. For more information on how to set up your machine to work with non-English characters, see Language Support.

Behavior Changes

• In Magic xpi 4.1, since the Magic.ini file took precedence in the Studio and the ifs.ini file took precedence in Runtime, you had to maintain your environment variables in both files. Now, in Magic xpi 4.5, the ifs.ini file always takes precedence over the Magic.ini file, both in the Studio and in Runtime.

• In the Monitor, during runtime, the server deletes all ODS records belonging to a completed FSID. In Magic xpi 4.1, these records appeared even when they were no longer active.

• Reconnecting the Debugger in the Studio: In Magic xpi 4.5, the Studio will try to reconnect when there are connectivity problems between the Debugger and the runtime project, according to a number of rules, such as several retries and timeouts. In Magic xpi 4.1, for these types of problems, the Studio terminated the debugging session.

• Defining a flat file structure is done using the List property.

• The keyboard combination for opening an existing project is now Ctrl+SHIFT+O instead of Ctrl+O. The keyboard combination for creating a new project is now Ctrl+SHIFT+N instead of Ctrl+N.

• Inserting a flow or business process is now done using the Project > Add menu.

• Starting the Debugger is done by pressing F5 instead of SHIFT+F7.

• When a project is running in Debug mode and the Studio is terminated, after the Studio stops publishing that it is alive, the running project will terminate internally. This prevents projects in Debug mode running without having a Studio controlling them. In addition, when attaching to a running project and moving it into Debug mode, if the Studio stops publishing that it is alive, the project will move back to production mode.

• The default project location is now under your My Documents directory, in the Magic folder.

• Setting how the Studio opens is done using the At Startup drop-down list. This is accessed by going to the Tools menu, clicking Options, and selecting Startup in the Environment section. This is similar to the Startup As property that was available in Magic xpi 4.1's Customize dialog box.

• The disabling, enabling, and deactivating of individual flows is now done through that flow's Properties pane.

• The IFC Model is now available as an option in the XML Properties. It is available for components with a static XML interface.

• Flow IDs in Magic xpi 4.5 are unique to a specific project, whereas in Magic xpi 4.1 flow IDs were unique to a business process.

• Business processes and flows are represented as folders on the disk with a number that is the ID of that business process or flow.

• Since version Magic xpi 4.5, the NOT operator requires parentheses. When you run the Checker on a project, parentheses are added to NOT expressions. However, the parenthesis will be seen only when you open the Expression Editor after the Checker process and when you make a change to the expression or click the Verify or OK button.

• BLOB variables in Save Message steps can now be saved to the file system instead of the database. The FILELOCATION column in the ifs_actlog table stores the value from the [MAGIC_IBOLT]ActivityBlobFileLocation flag concatenated with the file name when the project loads. The BLOB will be shown in the Magic Monitor whether it is saved in the BLOB variable or in the file system. If the BLOB is saved in the file system, the Magic Monitor will search the BLOB according to the FILELOCATION column. When clearing the Activity Log from the Magic Monitor, these BLOBs will be deleted whether they are saved to the database or on the disk.

• In Magic xpi 4.1, when running the Checker, the project was saved. As of Magic xpi 4.5, the project is not automatically saved, letting you revert changes that caused errors.

• The default value of the SpecialEventQSizeLimit flag was changed from 100 to 5000. (Since version: 4.5a)

• The SpecialExpReturnNull flag maintains backward compatibility when comparing a variable that has a Null value to an empty value.

• The Clear Mode property has been moved to the Project Properties window, and can now be used to clear ODS information only.

• Magic xpi does not have a default picture to handle xs:union field types. If your schema contains an xs:union field type, you need to add this type to the Default Data Format repository. During migration, if you had an xs:union field type and it was mapped, after the migration process you will get a Checker error letting you know that you need to define your xs:union field type. (Since version: 4.5a)

Terminology Changes

The following terms were changed:

• Services to utilities: This is referring to the Services that were in the Components pane in Magic xpi 4.1.

• The uniPaaS component has been renamed to the Magic xpa component.

• The System i connector has been renamed to the IBM i connector.

• The SugarCRM connector has been renamed to the Sugar connector.

• The Exchange 2007 connector has been renamed to the Exchange connector. This connector works with the Microsoft® Exchange 2007 Server and above.

• The Always use the new Picture node property was renamed to Always Use Custom Picture.

• The Exception Handling Flow property in database destinations was renamed as Error Handling Flow.

• The project's executable extension was changed from .ibs to .mgxpiproj.

• Compound Level Computation is now called Multi Update.

• Cross Reference has been renamed to Find Reference.

Non-Supported Features

The following features are no longer supported in Magic xpi:

• Rights Repository

• Security Groups Repository

• Users Repository

• Project Packager

• COM component: In migrated projects, during runtime, the COM triggers will be removed.

• EJB component: In migrated projects, during runtime, the EJB steps will be treated as NOP steps and triggers will be removed.

• Domino component as a trigger: In migrated projects, during runtime, the Domino triggers will be removed.

• W4 component: In migrated projects, during runtime, the W4 steps will be treated as NOP steps and triggers will be removed.

• ItemField component: In migrated projects, during runtime, ItemField components will be removed.

• Legacy monitor including the ifm.ini file

• Text Area tool

• The Find Reference feature is not available for resources and services. To find where a resource or service is used, use the Find Text option on the current project.

• Topology pane

• Business Process pane

• WS bridge

• SharedValGet and SharedValSet functions. For additional information, see the Migration Tool - Magic xpi 3.x and Above to Magic xpi 4.5 topic.

• Magic xpi 4.5 is no longer compatible with the Windows 2003 operating system. This is because by default, Microsoft does not support .NET Framework 4.5.2 (required by Magic xpi 4.5) with the Windows 2003 operating system.

• The Convert Email Encoding To ANSI and Include Email Plain Body flags.

• The Project Rename option has been removed. To rename a project, you can use the Save Copy As option instead.

The following features are currently not supported in Magic xpi:

• Import/Export

• Printing a project

• The Customize dialog box

• UDDI Server

• JSON schema elements that contain the word: not.