Child pages
  • General considerations for migrating applications from other application servers
Skip to end of metadata
Go to start of metadata

Migrating from other application servers

If you have developed Java EE assets that have been successfully deployed in other Java EE application server platforms, migration to Geronimo is typically just a matter of building a deployment plan and deploying your asset to your server. Review the following considerations to help you plan your migration.

  • Unless your asset is a very simple collection of servlets and JavaServer pages (JSPs), you will have to develop a deployment plan. See Creating deployment plans for more information.
  • If your Java EE asset uses external libraries, you will have to add the JAR files for those libraries to your server's repository and then add a matching dependency element to your deployment plan so the classloader can find them. You can add the libraries either manually or through the administrative console. See Adding JARs to the Geronimo repository for more information.
  • If your Java EE asset uses external enterprise Java beans (EJBs), your deployment plan will need to include ejb-ref tags if you use the remote home and remote interface or ejb-local-ref tags if you use the local home and local reference. These elements are not necessary for EJBs within the same application, because an ejb-link can be used in the standard Java EE deployment descriptor and then no WASCE-Specific configuration is necessary.
  • If your Java EE asset uses role based security constraints, you will need to add group definitions into the server's security realm or, if the roles need to be mapped to existing users or groups, you will need to include a security tag to your deployment plan.
  • To deploy your Java EE asset, you will need to invoke the deploy script, use the administrative console or the hot deploy feature. See Deploying and undeploying applications for more information.
  • If your Java EE asset uses any classes or interfaces that are unique to a different application server, in other words, classes or interfaces that are not defined in the Java EE specification, you will need to find alternatives and modify your asset as part of your migration.
  • If your Java EE asset relies on a particular database, you may need to migrate the data to a database accessible from your server.
  • If your Java EE asset uses a datasource reference to connect to a database, you will need to define a matching datasource in your server.
  • If your Java EE asset uses a JMS queue or topic, you will need to define a matching JMS queue or topic in your server.
  • If your Java EE asset uses JMS to interoperate with other components and those components do not support the Active MQ message broker, you will need to find an Active MQ bridge or a JMS client compatible with your partner, that can be integrated into the Geronimo framework.
  • No labels