Migrating an N-Tier Application Using Images

You can import existing application images running in a cloud and use them as custom images for a CloudCenter tenant.
This example describes a Siebel CRM application that uses an Oracle database with data running at the customer's location. The data is being migrated from a dedicated on-premises server to a cloud.

To migrate an N-tier application with data, using images, follow this process:

You need CloudCenter administrator privileges to perform this procedure.

  1. Back up the data running on the Siebel CRM application.
  2. Create an image for each tier in the application:
    1. The database with data.
    2. The Siebel CRM application with all dependencies.
  3. Identify the relevant Key ComponentsParameters and Macros , and Configuration Files for this application.
  4. Log into CCM UI and access Admin > Image:
    1. Click the Add New link to add a new image.
    2. In the Add a New Image page, fill in the fields to create a logical entry for your image in CloudCenter:
      • OS Type: The OS on which the image is based. For Siebel CRM, the OS is Linux.
      • Number of Network Interfaces: The base image dictates the number of NICs. See IP Allocation Mode for additional context.
  5. Map the logical CloudCenter Images  to your actual image:
    1. In the Image Mappings section, select the Cloud Type for the image from the dropdown list.
    2. Enter the Image ID associated with the Cloud Type.
    3. Select all applicable Instance Types supported for this image. You can also override the image cost by not modifying the cost.
    4. After adding the mapping, you can view the mapped image by clicking the image name. You can edit/convert/delete images after creating them.
    5. Repeat the step for each image associated with each tier in this application (for example, the database image, SiebelDB).
    6. Users will see the newly added images during their application deployment process.
  6. Configuration Files (or properties file) to include CloudCenter-defined system macros to automatically plug in the appropriate values for parameters defined in the configuration file. Alternately, you can pass these as arguments to install or configuration scripts.
  7. After modifying the configuration files with system macros, create a .war application package and include the updated configuration file.
  8. Upload the application data (packages, configuration files, backup data, SQL script, and other scripts) to your secure, shared directory in the Artifact Repository:
    1. Create an application directory under /storage/app/<application name>.
    2. Upload the components to the Application Repository to the newly created directory.
  9. If the application requires certain parameters to be defined or overridden (administrator, username, and password), include them in the Topology Modeler's Global Parameters tab.
  10. Define the application architecture and services using the Topology Modeler. For each tier, use the Properties panel to provide additional details. For example:
    1. Siebel Database tier: Parameters, username, password, the path for the database script that has the backup data from a previous environment, and so forth.
    2. Siebel CRM tier: Define the path for the application binary file and the configuration file.
    3. Similarly, provide the dependent details for other applicable tiers as well.
  11. Save the N-Tier app profile as Siebel CRM application. Access your new application from the Apps tab and verify your changes for each tier. The application is now ready for deployment.
  12. Deploy the Application:
    1. Depending on the hardware requirement and application-specific requirements, select the cloud and instance types from the displayed list.
    2. Select the required Instance Types .
  13. Submit the application for deployment. The CCM sends the application package information (JSON package) to the CCO.
  14. View the deployment progress in the Status field.
  15. SSH or VNC to the cloud VM for additional troubleshooting access or to run additional commands and scripts.
  16. Once the deployment is complete, click the Access link (access URL) to open the IP address for this application. You may need to specify the full path in the context of the application in the Topology Builder's Basic Information pane.
  17. Use the full path URL to access the migrated Siebel CRM application.

 

  • No labels