Migration

Edit online

Migration with Application Modernization Accelerator (AMA) involves analyzing existing applications, assessing their compatibility with modern cloud platforms (like IBM Cloud), and providing guidance for migrating them to containerized or cloud-native environments.

For more information, see creating a project in IBM Cloud.

How to apply EASeJ environment-specific configuration files

The migration plan from the Application Modernization Accelerator for IBM Enterprise Application Service for Java (EASeJ) includes three pre-configured files: server.xml, localConfig.xml, and EASeJConfig.xml. The config file server.xml serves as the core configuration file and acts as the default setup for the application server. The config files localConfig.xml and EASeJConfig.xml contain environment-specific settings.

Two environment-config files are provided because the configuration settings and security responsibilities differ between Liberty Dev Mode and EASeJ. In Dev Mode, developers are responsible for configuring their own secure server for Java applications. This includes defining TLS keystores and truststores, providing JDBC drivers, and MQ adapters, and other necessary components.

In contrast, EASeJ runs on a pre-secured, managed Kubernetes cluster where IBM handles operations and compliance. For example, TLS, certificate rotation, and secret storage are all managed by EASeJ, significantly reducing the operational overhead for developers.

Configuration for local development

The recommended approach for deploying applications on EASeJ is to implement modernization code changes, test them using Liberty Dev Mode, and then deploy to the cloud. This helps catch issues early and reduces the risk of deployment failures.

As part of this workflow, use the localConfig.xml env-config file to override configuration settings specifically for Dev Mode.

Procedure

  1. Place the main server configuration file in config directory.

    Place server.xml in the src/main/liberty/config directory. Liberty will automatically detect it and copy it to <wlp_install_dir>/usr/servers/<server_name> during server startup.

  2. Place the environment configuration file in the config/configDropins/overrides directory.

    Place localConfig.xml in src/main/liberty/config/configDropins/overrides directory. Liberty will automatically detect it and copy it to <wlp_install_dir>/usr/servers/<server_name>/configDropins/overrides during startup.

    Configuration in configDropins/overrides takes precedence over server.xml.

Configuration for deployment to EASeJ

After testing the code in Liberty Dev Mode, users can deploy to the cloud by applying EASeJ-specific configuration settings using the EASeJConfig.xml env-config file.

The file includes the DB2 driver and MQ adapter config, enabling their use in the cloud environment. The Keystore and truststore configurations are not included, as they are managed by EASeJ.

Procedure

  1. Place the main server configuration file in the config directory.

    Place server.xml in the src/main/liberty/config directory. Liberty will automatically detect it and copy it to <wlp_install_dir>/usr/servers/<server_name> during server startup.

  2. Place the environment configuration file in the config/configDropins/overrides directory.

    Place EASeJConfig.xml in the src/main/liberty/config/configDropins/overrides directory. Liberty will automatically detect it and copy it to <wlp_install_dir>/usr/servers/<server_name>/configDropins/overrides during startup.

    Configuration in configDropins/overrides takes precedence over server.xml.