| Forte for Java 4, Enterprise Edition Getting Started Guide |    
|
| Forte for Java 4, Enterprise Edition Getting Started Guide |
|
| C H A P T E R 6 |
|
Customizing Your Installation |
This chapter contains information to assist you in customizing your installation of the Forte for Java 4, Enterprise Edition. It includes information about the PointBase Server 4.2 Restricted Edition and the IDE's internal UDDI Registry server.
The PointBase Server 4.2 Restricted Edition is available for installation with the Forte for Java 4 IDE. You can use other databases with the IDE by configuring the JDBC
enabled database drivers for those databases.
|
Note - The following instructions assume you have already installed the PointBase Server 4.2 Restricted Edition during the IDE installation. |
PointBase Server 4.2 Restricted Edition is the default database that is provided with the Forte for Java 4 IDE installation. For information on using this database and database tables, see the PointBase documentation at either ffj-install-dir/pointbase/server/GettingStarted.html or ffj-install-dir/pointbase/client/GettingStarted.html.
You have to start the PointBase database server before you can use it, whether you want to access a PointBase database from an application you developed using the IDE or you want to create your own tables or database with PointBase software.
To start the PointBase database server:
Choose Tools 
PointBase Network Server Start Server from the main window of the IDE.
Alternatively, on Microsoft Windows systems, start the PointBase server by choosing
Forte for Java 4.0 EE PointBase Network Server Server from the Start menu.
The PointBase 4.2 window appears.
|
Note - The following action stops only the PointBase database server that was started by choosing Tools |
To stop the PointBase database server:
Choose Tools PointBase Network Server Stop Server from the main window of the IDE or choose Server Shutdown! from the PointBase 4.2 window.
To start a PointBase console, do the following:
In a supported Solaris or Red Hat Linux environment, type:
$ sh ffj-install-dir/pointbase/client/Console |
On Microsoft Windows systems, start the PointBase client console by choosing Forte for Java 4.0 EE PointBase Console from the Start menu.
A dialog named "Connect to Database" appears. Click OK to continue.
To stop the client console, terminate the window from which it is running.
The J2EE Reference Implementation 1.3.1 is preconfigured to use the PointBase Server 4.2 Restricted Edition server included with the IDE. Starting the J2EE Reference Implementation 1.3.1 server does not start the PointBase server. You must start the PointBase Server 4.2 Restricted Edition server separately, as previously instructed in this chapter.
If, however, you want to create a different PointBase database for your tables, you need to use the $J2EE_HOME/bin/j2eeadmin tool to update the $J2EE_HOME/config/resource.properties file. The $J2EE_HOME is set to the ffj-install-dir/j2sdkee1.3.1 directory.
The j2eeadmin syntax to create a different PointBase database is as follows:
j2eeadmin -addJdbcDatasource jndi_name url |
For example, in a Solaris environment, you might type the following at the command line:
$ $J2EE_HOME/bin/j2eeadmin -addJdbcDatasource jdbc/DB1 jdbc:pointbase:server://localhost/yourdatabase |
Alternatively, you can manually edit the $J2EE_HOME/config/resource.properties file and modify the jdbc.resources variable, as follows:
jdbc.DataSource.0.url=jdbc:pointbase:server://localhost/your-database |
The following information applies to database drivers other than the driver for the PointBase Server 4.2 Restricted Edition database.
You must place database driver files in the Forte for Java lib/ext directory before you start the Forte for Java 4 IDE. If you do not do this, the dbschema wizard does not enable you to select the proper database driver when you create a new schema. You cannot mount the driver file in the IDE's Explorer, nor can you simply place the driver file in the CLASSPATH environment variable. You must copy the driver file into the lib/ext folder.
The same database driver must also be added to the $J2EE_HOME/lib/system directory so that the application server is aware of the new database driver. Read the information contained in ffj-install-dir/j2sdkee1.3.1/doc/release/
ConfigGuide.html#12442 for more information on required steps for adding more database drivers to the J2EE Reference Implementation 1.3.1 application server.
For more information on database configuration and adding new database drivers, see http://www.sun.com/forte/ffj/resources/articles/configdb.html.
A single-user, internal UDDI registry is bundled with the IDE as a convenience for end-to-end testing of your development process. This registry runs in a dedicated Tomcat server, which the IDE starts and stops automatically when you start and stop the registry server.
|
Note - The internal UDDI registry is configured with a single user. The name is testuser and the password is testuser. Set this name and password as the default for the internal registry. |
To start the internal UDDI registry server:
1. Expand the UDDI Server Registry node in the Explorer's Runtime tabbed pane.
You should see the Internal UDDI Registry node.
2. Right-click the Internal UDDI Registry node and choose Start Server.
The IDE's Output window displays server startup messages. You might also see messages stating that the IDE is stopping a previous Tomcat server process.
|
Note - If the internal UDDI registry server is already running, the Start Server menu item is inactive. |
To stop the internal UDDI registry server:
1. Expand the UDDI Server Registry node in the Explorer Runtime tabbed pane.
You should see the Internal UDDI Registry node.
2. Right-click the Internal UDDI Registry node and choose Stop Server.
Server stop messages are displayed.
|
Note - If the internal UDDI registry server is not running, the Stop Server menu item is inactive. |
| Forte for Java 4, Enterprise Edition Getting Started Guide | 816-4063-10 |
|
Copyright © 2002, Sun Microsystems, Inc. All rights reserved.