Run J2EE™ Pet Store Application 1.1.2 with the Borland® Enterprise Server™ 5.0.1

• Download and Install Borland Enterprise Server
• Download the J2EE Pet Store 1.1.2 Application
• Download the Borland Pet Store Collateral
• Deploy Datasource Defiinitions for Pet Store
• Deploy Pet Store Application to Borland Enterprise Server
• Access Pet Store
• Running Pet Store with an Oracle Database
• Support

If you do not already have Borland Enterprise Server then you can download a fully functional trial copy of Borland Enterprise Server from http://www.borland.com/bes.

Follow the instruction in the Installation Guide.

Download the Sun's Java(TM) Pet Store 1.1.2 from http://java.sun.com/j2ee/download.html#blueprints and unzip it, or use the provided EAR in the Borland Pet Store collateral.

The remainder of this document will refer to the unzipped jps1.1.2 directory as <jps1.1.2>.

Download the Borland Pet Store collateral from http://www.borland.com/devsupport/bes/downloads/deployathon/petstore/borland_petstore112.zip and extract into <jps1.1.2>.

This will result in a the creation of a <jps1.1.2>\borland directory and a <jps1.1.2>\src\petstore\src\borland_build.bat file.

Datasource definitions and Cloudscape JDBC driver jars have been provided in the accompanying collateral:

• <jps1.1.2>\borland\cloudscape\jndi-definitions.xml.
• <this_download>\lib\cloudscape\RmiJdbc.jar and <this_download>\lib\cloudscape\cloudclient.jar (you must use these provided versions of the Cloudscape Driver jars!)

The datasources are configured to use Cloudscape driver datasources (soon will be JDataStore, but not today). Edit the <driver-datasource> entries to match your Cloudscape configuration.

First deploy the Cloudscape driver and restart the server to get it on the server's classpath:

• Run up the Borland Enterprise Server Console, select the Tasks menu, select the Deployment sub-menu, and select the Deploy J2EE modules to a partition.
• Select Add..., browse to <jps1.1.2>\borland\lib, and select RmiJdbc.jar and cloudclient.jar, then OK
• Then:
  • If you only have one server and partition running then simply click on OK.
  • Otherwise:
    • Click on Target partition and select the your target server and partition
    • Click OK

Then deploy the jndi-definitions to the server:

• Run up the Borland Enterprise Server Deployment Descriptor Editor and select the Open J2EE archive or descriptor.
• Browse to <jps1.1.2>\borland and select jndi-definitions.xml then OK
• Run up another Borland Enterprise Server Deployment Descriptor Editor and select the Open J2EE archive or descriptor.
• Browse to $BES_INSTALL/var/servers/$SERVER_NAME/partitions/standard, where $BES_INSTALL is the path for your Borland Enterprise Server installation directory, and $SERVER_NAME is the name you provided for your Borland Enterprise Server installation, and select jndi-definitions.xml then OK
• Copy the contents of <jps1.1.2>\borland\jndi-definitions.xml (inside, but not including the jndi-definitions tags) to $BES_INSTALL/var/servers/$SERVER_NAME/partitions/standard/jndi-definitions.xml. Then select the File menu and select Save, to save your changes to $BES_INSTALL/var/servers/$SERVER_NAME/partitions/standard/jndi-definitions.xml.
• Run up the Borland Enterprise Server Console to restart the standard partition

You can either just deploy the borland_petstore.ear provide in <jps1.1.2>\borland\borland_petstore112.ear, download a provided borland_petstore112.ear standalone and deploy it, or take a virgin Sun Pet Store and deploy that.

Downloading the provided borland_petstore112.ear standalone:

You can download the provided borland_petstore112.ear standalone from http://www.borland.com/devsupport/bes/downloads/deployathon/petstore/borland_petstore112.ear

Deploying the provided borland_petstore112 ear:

Run up the Borland Enterprise Server Console, select the Tasks menu select the Deployment sub-menu, and select the Deploy J2EE modules to a partition.

• Select Add... and browse to either
  • <jps1.1.2>\borland (if using the borland_petstore112.zip collateral package), or
  • The location where you downloaded the standalone borland_petstore112.ear
• Select borland_petstore112.ear, then OK
• Then:
  • If you only have one server and partition running then simply click on OK.
  • Otherwise:
    • Click on Target partition and select the your target server and partition
    • Click OK

Deploying a virgin Sun Pet Store:

Follow the instructions detailed at http://www.borland.com/devsupport/bes/downloads/deployathon/petstore/readme112virgin.html to deploy a virgin Sun Pet Store to Borland Enterprise Server 5.0.1.

Then deploy the resulting EAR file to the server as for "Deploying the provided borland_petstore112 ear" above.

Browse to http://localhost:8080/estore

For running Pet Store with an Oracle Database, datasource definitions and an Oracle JDBC driver have been provided in the accompanying collateral:

• <jps1.1.2>\borland\jndi-definitions.xml.
• <this_download>\lib\oracle\classes12_01.zip (you must use this version of the Oracle Driver!)

The datasources are configured to use Oracle driver datasources. Edit the <driver-datasource> entries to match your Oracle configuration.

First deploy the Oracle driver and restart the server to get it on the server's classpath:

• Run up the Borland Enterprise Server Console, select the Tasks menu, select the Deployment sub-menu, and select the Deploy J2EE modules to a partition.
• Select Add... and browse to <jps1.1.2>\borland\lib and select classes12_01.zip then OK
• Then:
  • If you only have one server and partition running then simply click on OK.
  • Otherwise:
    • Click on Target partition and select the your target server and partition
    • Click OK

Then deploy the jndi-definitions to the server:

• Run up the Borland Enterprise Server Deployment Descriptor Editor and select the Open J2EE archive or descriptor.
• Browse to <jps1.1.2>\borland and select jndi-definitions.xml then OK
• Run up another Borland Enterprise Server Deployment Descriptor Editor and select the Open J2EE archive or descriptor.
• Browse to $BES_INSTALL/var/servers/$SERVER_NAME/partitions/standard, where $BES_INSTALL is the path for your Borland Enterprise Server installation directory, and $SERVER_NAME is the name you provided for your Borland Enterprise Server installation, and select jndi-definitions.xml then OK
• Copy the contents of <jps1.1.2>\borland\jndi-definitions.xml (inside, but not including the jndi-definitions tags) to $BES_INSTALL/var/servers/$SERVER_NAME/partitions/standard/jndi-definitions.xml. Then select the File menu and select Save, to save your changes to $BES_INSTALL/var/servers/$SERVER_NAME/partitions/standard/jndi-definitions.xml.
• Run up the Borland Enterprise Server Console to restart the standard partition

Follow the instructions detailed at http://www.borland.com/devsupport/bes/downloads/deployathon/petstore/readme112virgin.html for using the Oracle settings for deploying a virgin Sun Pet Store to Borland Enterprise Server 5.0.1.

Then deploy the resulting EAR file to the server as for "Deploying the provided borland_petstore112 ear" above.

The j2eeblueprints interest list is the place to get answers to questions about running the Deployathon with Java 2 SDK, Enterprise Edition 1.2.1 for Solaris. To join the interest list, send an email to listserv@java.sun.com. Specify subscribe j2eeblueprints-interest yourlastname yourfirstname in the body of the email.