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

- Previous: Migrating Proprietary Extensions
- Next: Migrating JDBC Code

# Migrating UIF

The Application Server does not support the use of Unified Integration Framework (UIF) API for applications. Instead, it supports the use of J2EE Connector Architecture (JCA) for integrating the applications. However, the applications developed in Application Server 6.5 use the UIF. In order to deploy such applications to the Application Server, migrate the UIF to the J2EE Connector Architecture. This section discusses the prerequisites and steps to migrate the applications using UIF to Application Server.

Before migrating the applications, ensure that the UIF is installed on Application Server 6.5. To check for the installation, follow either of the following approaches:

## Checking in the Registry Files

UIF is installed as a set of application server extensions. They are registered in the application server registry during the installation. Search for the following strings in the registry to check whether UIF is installed.

Extension Name Set:

- Extension DataObjectExt-cDataObject

- Extension RepositoryExt-cLDAPRepository

- Extension MetadataService-cMetadataService

- Extension RepoValidator-cRepoValidator

- Extension BSPRuntime-cBSPRuntime

- Extension BSPErrorLogExt-cErrorLogMgr

- Extension BSPUserMap-cBSPUserMap

The registry file on Solaris Operating Environment can be found at the following location:

AS_HOME/`AS/registry/reg.dat`

### Checking for UIF Binaries in Installation Directories

UIF installers copy specific binary files in to the application server installation. Successfully finding the files listed below, indicates that UIF is installed.

The location of the following files on Solaris and Windows is:

AS_HOME`/AS/APPS/bin`

List of files to be searched on Solaris:

- `libcBSPRlop.so`

- `libcBSPRuntime.so`

- `libcBSPUserMap.so`

- `libcDataObject.so`

- `libcErrorLogMgr.so`

- `libcLDAPRepository.so`

- `libcMetadataService.so`

- `libcRepoValidator.so`

- `libjx2cBSPRuntime.so`

- `libjx2cDataObject.so`

- `libjx2cLDAPRepository.so`

- `libjx2cMetadataService.so`

List of files to be searched on Windows:

- `cBSPRlop.dll`

- `cBSPRuntime.dll`

- `cBSPUserMap.dll`

- `cDataObject.dll`

- `ErrorLogMgr.dll`

- `cLDAPRepository.dll`

- `cMetadataService.dll`

- `cRepoValidator.dll`

- `jx2cBSPRuntime.dll`

- `jx2cDataObject.dll`

- `jx2cLDAPRepository.dll`

- `jx2cMetadataService.dll`

Before migrating the UIF to Application Server, ensure that the UIF API is being used in the applications. To verify its usage:

- Check for the usage of `netscape.bsp` package name in the Java sources

- Check for the usage of `access_cBSPRuntime.getcBSPRuntime` method in the sources. You must call this method to acquire the UIF runtime.

Contact appserver-migration@sun.com for information about UIF migration to the Application Server.

- Previous: Migrating Proprietary Extensions
- Next: Migrating JDBC Code

- © 2010, Oracle Corporation and/or its affiliates