Configuring Profiles on exteNd Application Server
Articles and Tips: tip
Research Engineer
Novell Appnotes
jfischer@novell.com
01 May 2003
The following is from the new "Web Services" DeveloperNet Univeristy course available on the Web at http://developer.novell.com/education/tutorials/web/ .
One of the main objectives of Java is to be completely portable. While there are a few issues to overcoming 100% portability, great strides have been made to help achieve this. In the Web Application arena, not only do you have to be concerned with the portability of your application for clients, but for servers as well.
While most companies standardize on Java application servers, it is still common to find more than one type of application server used in the production environment. As a developer, you want to be sure that you can compile and build your program so that you are sure it will run on multiple application servers, such as exteNd Application Server, Tomcat, BEA, and others.
Novell exteNd Workbench allows you to create profiles to compile your web application for different application server platforms. The profile will contain the type of server, deployment directory, and URL to access the application. You can also create a separate profile to manage the database you are using and the UDDI registry information. The JDBC driver, URL and DataSource Name is contained within the database profile. The inquiry and publisher API is stored within the Registry profile.
Creating a Server, Database, or Registry Profile
To create a Server, Database, or Registry profile in exteNd Workbench, follow the steps below:
Open exteNd Workbench.
Open the project you want to deploy.
From the Edit > Profiles.
Click the Servers tab.
Click the New button.
In the Profile Name box, type a name for the profile. For example, if the profile will deploy web applications to an exteNd application server, then you could call the profile exteNd.
Select the type of application server you are going to publish to from the drop down menu.
In the Deployment Tools Directory box, browse to the location in the file system of the application server where the deployed files should go to deploy the application.
If the server you are using supports Rapid Deployment, you can browse to the location where Workbench should copy the rapid deployment files.
In the Server Name box, type in the URL and port number if necessary to access this server. For example, you could type in http://localhost if the application is deployed on the local server.
Creating a Database Profile
To create the Database profile in exteNd Workbench, follow the steps below:
Open exteNd Workbench.
Open the project you are going to deploy.
Select Edit > Profiles.
Select the Database tab.
Click the New button.
Enter a name for the profile.
Enter the JDBC driver. For example, if you are using the JDBC-ODBC driver developed by Sun, type in sun.jdbc.odbc.JdbcOdbcDriver.
Enter the JDBC URL. For example, if you are using the JDBC-ODBC driver developed by Sun, type in jdbc:odbc:name_of_db driver name.
Type in the name of the SQL catalog if you are using catalogs.
Type in the name of the DataSource.
Click the Test button to make sure the connection can be established successfully.
Creating a Registry Profile
To create the Registry profile in exteNd Workbench, follow the steps below:
Open exteNd Workbench
Open the project you are going to deploy.
Select Edit > Profiles.
Select the Registry tab.
Click the New button.
Enter a name for the profile.
Enter an inquiry API URL.
Enter a publisher API URL.
Enter a username and credential if necessary.
Changing a Profile
To change a profile, follow the steps below:
Open exteNd Workbench.
Open the project you are going to deploy.
Select Edit > Profiles.
Select the Server, Databases, or Registry tab.
Select the profile name you already created in the drop down menu.
Click OK .
* Originally published in Novell AppNotes
Disclaimer
The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.