Sun Java System Application Server Platform Edition 8.1 2005Q2 Update 2 Upgrade and Migration Guide

- Previous: Preparing for Migrating the iBank Application
- Next: Chapter 8 Migration Tools and Resources

# Manual Steps in the iBank Application Migration

Most of the migration is done by the Migration Tool. There are some aspects of migration that must be done manually. These steps are documented in the Migration Tool’s user’s guide and the documentation for the iBank sample application.

## Configuring Database Connectivity

In order to deploy an application to the target server, you must add a connection pool, add a JDBC resource and a persistence manager.

This section discusses the following topics:

- Adding a Connection Pool

- Adding a JDBC Resource

- Adding a Persistence Manager

Note –

Before you begin these steps, make sure that the domain to which the application will be deployed is in the running state. These instructions assume that the application will be deployed to the default domain, domain1.

Use the asadmin utility in the Application Server bin directory to perform these tasks.

### Adding a Connection Pool

A JDBC connection pool is a group of reusable connections for a particular database. Because creating each new physical connection is time consuming, the server maintains a pool of available connections to increase performance. When an application requests a connection, it obtains one from the pool. When an application closes a connection, the connection is returned to the pool.

Use the `asadmin create-jdbc-connection-pool` command to add a connection pool to the server. The syntax of the command is given below.

    asadmin create-jdbc-connection-pool
         --user  admin_user
         --password admin_password
         --host localhost
         --port portno
         --datasourceclassname dsclassname
         --property User=ibank_user:Password=ibank_user:URL_PROP=db_url TMB

where, dsclassname is:

- `oracle.jdbc.pool.OracleDataSource` for Oracle

- `com.pointbase.jdbc.jdbcDataSource` for PointBase

URL_PROP is:

- `url` for Oracle

- `DatabaseName` for PointBase

db_url is:

- `jdbc:oracle:thin:@`ORACLE_HOST`:1521:SID` for Oracle, where ORACLE_HOST is the machine name/IP address on which the database is installed, and SID is the System ID of the Oracle database.

- `jdbc:pointbase:server://`POINTBASE_HOST:9092`/migration-samples` for Pointbase, where POINTBASE_HOST is the machine name/IP address on which the database is installed. This will be localhost in most cases.

### Adding a JDBC Resource

A JDBC resource (data source) provides applications with a means of connecting to a database. Before creating a JDBC resource, you must first create a JDBC connection pool.

Use the `asadmin create-jdbc-resource` command to add resource.

`asadmin create-jdbc-resource --user` admin_user `--password` admin_password `--host localhost --port` portno `--connectionpoolid TMB jdbc/IBank`

### Adding a Persistence Manager

A persistence manager is required for backward compatibility. To run on version 7 of the Application Server, a persistent manager resource was required for applications with container-managed persistent beans (a type of EJB component).

Use the `asadmin create-persistence-resource` command.

`asadmin create-persistence-resource --user` admin_user `--password` admin_password `--host localhost --port` portno `--connectionpoolid TMB --factoryclass com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerFactoryImpljdo/pmf`

## Assembling Application for Deployment

Application Server primarily supports the J2EE model wherein applications are packaged in the form of an enterprise archive (EAR) file (extension .ear). The application is further subdivided into a collection of J2EE modules, packaged into Java archives (JAR, extension .jar) for EJBs and web archives (WAR, extension .war) for servlets and JSPs.

All the JSPs and Servlets must be packaged into WAR file, all EJBs into the JAR file and finally the WAR and the JAR file together with the deployment descriptors in to the EAR file. This EAR file is a deployable component.

## Using the asadmin Utility to Deploy the iBank Application on Application Server

The last step is to deploy the application on Sun Java System Application Server 8.1. The process for deploying an application is described below:

The Sun Java System Application Server 8.1 asadmin command includes a help section on deployment that is accessible from the Help menu.

The command line utility `asadmin` can be invoked by executing `asadmin.bat` file in Windows and `asadmin` file in Solaris Operating Environment that is stored in Application Server’s installation’s `bin` directory.

At `asadmin` prompt, the command for deployment looks like this:

`asadmin> deploy -u` username `-w` password `-H` hostname `-p` adminport absolute_path_to_application

After restarting the Application Server, open a browser and go to the following URL to test the application:

`http://<`machine_name`>:<`port_number`>/ibank`

When prompted, enter one of the available user names and passwords. The main menu page of the iBank application displays.

- Previous: Preparing for Migrating the iBank Application
- Next: Chapter 8 Migration Tools and Resources

- © 2010, Oracle Corporation and/or its affiliates