Options (Magic xpi 3.x)
In the Options screen:
-
Select the Create Shortcut Folder check box to create a shortcut folder on your desktop that includes shortcuts for the Magic xpi Studio, Magic xpi Monitor, Magic xpi Server, and the uniPaaS Studio. The default is checked.
-
Select the Install License Server check box to install the license server to manage the licensing for the Magic xpi Servers used in your projects. For more information, see the, Magic xpi Licenses section. The default is unchecked.
-
Select the Install Sample Projects check box to install a set of Magic xpi projects that help you understand how to work with different Magic xpi features and functionality. The default is unchecked.
-
Select the Install Web Service Framework check box to install the Systinet Web service. The default is checked.
If there is a properly installed Java 6.0, Magic xpi uses it. Otherwise, Magic xpi installs its own. Magic xpi searches the registry for the Java installation and uses the path to Java that it finds. Therefore, if there is a mismatch between the registry and the actual installation, the SSJ installation fails. If this happens, you can install the SSJ manually. Click here for more information.
|
Note:
|
When installing a new Magic xpi version, the new Systinet installation upgrades the existing Systinet installation to version 6.6. If an earlier version was already installed on this machine, this Systinet upgrade has two side effects:
-
Getting the "java.lang.UnsupportedClassVersionError: Bad version number in .class file …" error in the Studio and the Server. This is because jars that are compiled by JDK 6.0 (such as the uniRequester.jar and the uniSSJ.jar) are loaded by the 5.0 JVM that is used by Magic xpi. You will get this error in any component that uses Java, such as: Salesforce, Email, SharePoint, Dynamics CRM, and Web Services.
-
The new Systinet version cannot be used by versions up to V3.2 SP1b.
If you want to use V3.2 SP2a and any version up to V3.2 SP1b on the same machine, you will need to maintain two versions of Systinet and use only one at a time.
You can do this by renaming or removing the WASP_HOME environment variable and renaming the existing Systinet folder prior to the new Magic xpi installation. The result will be a new installation of Systinet 6.6, and the WASP_HOME environment variable will point to this version.
When using any version up to V3.2SP1b, you need to point the WASP_HOME environment variable to the Systinet 6.5.2 installation. When using V3.2 SP2a, you need to point the WASP_HOME environment variable to the Systinet 6.6 installation.
|
|
When you have finished with this screen, click Next to proceed to the Broker Configuration screen.
