Skip Navigation Links | |
Exit Print View | |
![]() |
Upgrading to Oracle Java CAPS 6.3 Java CAPS Documentation |
Overview of Upgrading to Java CAPS 6.3
Upgrading From Release 5.0.5 - 5.1.3 to Release 6.3
Exporting and Importing Projects and Environments
To Use Enterprise Designer to Export Projects and Environments
To Use a Command Line to Export Projects and Environments
Upgrading From Release 6.x to Release 6.3
The process to upgrade from release 5.0.5 and earlier to release 6.3 has changed considerably. With release 5.1.3 and earlier, you performed an in-place installation. Now, you install Java CAPS 6.3 into a new directory, export 5.1.3 and earlier Projects and Environments and then import them into release 6.3 using the NetBeans IDE.
There are two ways to export your old Projects and Environments and create an external file:
Use Enterprise Designer's export function
Use a command-line script
Perform the following steps to upgrade from a 5.x release of Java CAPS to release 6.3.
Tip - These steps include installing Java CAPS. See one of the following topics for complete instructions on how to install:
Before beginning an installation, ensure that you are familiar with the contents of Planning for Oracle Java CAPS 6.3 Installation .
Note that a default Java CAPS installation does not install the complete set of products that were installed in previous versions. You might need to manually install some additional components, such as Adapters or other add-ons.
Perform one of the following procedures to export existing Projects and import them into the new Java CAPS environment.
Tip - When exporting a Project, note the following:
The exported Project may have references to elements that are in other Projects. A list of such references is generated during the export process.
Project deployment profiles are not exported, because they have references to both Project and Environment elements that are not required at the Project level.
Before You Begin
Before beginning the process of exporting Projects and Environments from prior releases of Java CAPS 5.1.0–5.1.3 or ICAN Suite 5.0.5, it is recommended that you acquaint yourself with the steps to complete the task in the appropriate version of the eGate Integrator User's Guide.
See the notes under Upgrading From Release 5.0.5 - 5.1.3 to Release 6.3 for links to more information.
This includes certain adapters and add-ons, certain core components like Oracle Java CAPS Master Index, and so on.
Tip - You can view a list of installed products for Java CAPS 6.3 on the Suite Uploader, which can be accessed from a web browser if the Repository is started. The URL is http://host-name:port-number.. The default port number is 12000.
Record the settings for your Projects and Environments before exporting them. You will need this information when you reset the properties.
Note - If you do not have any existing Environments in your Repository, the Environment panes are empty.
The Save As dialog box appears. A file name is already defined by adding the ZIP extension to the Project name.
Note - You can change the export file name.
The Export Manager dialog box reappears.
This process may take a few minutes. The Export Status message box appears after the file has been exported successfully.
A warning dialog box appears with a reminder to save any unsaved changes.
The Import Manager dialog box appears.
The Project appears in the Projects Window.
Before You Begin
You can export a Project, an Environment, or a Project and an Environment using a command-line script. Before beginning the process of exporting Projects and Environments from prior releases of Java CAPS 5.1.0–5.1.3 or ICAN Suite 5.0.5, it is recommended that you acquaint yourself with the steps to complete the task in the appropriate eGate Integrator User's Guide.
Location of Script File
JavaCAPS_install_dir\repository\util\exportProject.bat
or
JavaCAPS_install_dir/repository/util/exportProject.sh
Command Syntax
exportProject username password branch_name export_file project_name environment_name
where:
branch_name is the name of the Repository branch to contain the Project or Environment you are exporting.
export_file is the name and path for the archive file to contain the Project or Environment you are exporting.
project_name is the name of the Project you are exporting. You can export multiple Projects by listing them one after another, separated by a plus sign (+). If you do not export a Project, leave this parameter as an empty string ("").
environment_name is the name of the Environment you are exporting. You can export multiple Environments by listing them one after another, separated by a plus sign (+). If you do not export an Environment, leave this parameter as an empty string ("").
Note - The project_name and environment_name variables assume that the objects reside in the same repository directory as the script file you are using.
![]() | Caution - Project names should not include special characters such as a comma ( , ), single quote ( '), or double quote ( " ). If any of these characters are used, you must escape them when using the exportProject command-line tool. |
See the notes under Upgrading From Release 5.0.5 - 5.1.3 to Release 6.3 for links to more information.
This includes certain adapters and add-ons, certain core components like Oracle Java CAPS Master Index, and so on.
Tip - You can view a list of installed products for Java CAPS 6.3 on the Suite Uploader, which can be accessed from a web browser if the Repository is started. The URL is http://host-name:port-number.. The default port number is 12000.
exportProject username password branch_name export_file project_name environment_name
For example, to save the Project myProject to the file c:\project1export.zip with the default login, the command would be similar to the following:
exportProject admin adminadmin C:\JavaCAPS5\project1export.zip myProject.
A warning dialog box appears with a reminder to save any unsaved changes.
The Import Manager dialog box appears.
The Project appears in the Projects Window.
Note - When importing a Project, note that:
Existing Projects are not affected by an imported Project.
During import, if a Project with the same name as the Project being imported already exists in the target Repository, an error message informs you that the existing file will not be overwritten.
References are validated during import.
Project deployment objects are not imported.
![]() | Caution - Due to configuration changes from version 5.0.x, certain properties might be reset to their default value. Specifically, you should verify file names and directories defined for Adapters, but other properties might have changed as well. For Projects containing MSMQ Adapters, be sure to verify both sets of properties because some properties were changed and new properties were added since version 5.1.3. |
Once you have imported all previous Projects and Environment into Java CAPS 6.3, you need to redeploy and in some cases reconfigure the Projects.
![]() | Caution - Be sure to verify the Adapter properties in the Connectivity Maps and Environments. |