Server User Manual
Table Of Contents
- Developing Applications for J2EE™ Servers
- Contents
- Ch 1: Introduction
- Ch 2: Programming for the Java 2 Platform, Enterprise Edition
- Ch 3: Creating applications with J2EE technologies
- Ch 4: Configuring the target server settings
- Ch 5: Using JBuilder with Borland servers
- Configuring Borland servers in JBuilder
- Making the ORB available to JBuilder
- Configurations, partitions, partition services, and J2EE APIs
- Starting the configuration or server
- Remote deploying
- Remote debugging
- Web module workarounds
- Displaying the Borland Management Console in JBuilder
- International issues
- Borland servers and JDataStore 7.0
- Ch 6: Using JBuilder’s CORBA tools
- Ch 7: Using JBuilder with BEA WebLogic servers
- Ch 8: Using JBuilder with IBM WebSphere servers
- Ch 9: Using JBuilder with JBoss servers
- Ch 10: Using JBuilder with Tomcat
- Ch 11: Editing J2EE deployment descriptors
- Ch 12: Integrating with Enterprise Information Systems
- Ch 13: Building J2EE modules
- J2EE modules
- Setting module build properties
- Adding custom file types
- Sample build scenarios
- EJB JAR without any bean classes
- EJB JAR with custom files
- EJB JAR without EJB designer XML descriptors
- WAR with custom descriptor(s) in the WEB-INF directory
- WAR without any classes
- WAR with custom class filters
- WAR with custom file types
- EAR with custom files
- RAR with classes and dependencies
- Application client module with classes and dependencies
- Improving module build performance
- Index
78 Developing Applications for J2EE Servers
Deploying
8 Set the Host field to the host name where the Deployment Manager is running.
9 Set the Port field to the port number of the Deployment Manager.
10 Set the User Name and Password fields if they are required; for example, if security
is enabled.
Deploying locally
To deploy locally to a server which is not running,
1 Right-click the node you want to deploy in JBuilder’s project pane and choose
Properties.
2 Select Deployment in the tree and click the Connection tab.
3 Set the Connection Type to NONE.
If the connection type is set to NONE, deployment actions performed while the server
is running won’t start or stop the deployed module.
WebSphere Server 4.0
If you are using WebSphere 4.0 Advanced Edition, you must create an EAR group that
contains your beans. You then deploy the EAR group. For more information about
creating EAR groups, see “Creating an EAR file” in Developing Applications with
Enterprise JavaBeans.
Enterprise|Server Deployment displays a WebSphere Deployment dialog box.
Configure your deployment settings with this dialog box. JBuilder passes the settings
you specify on to the WebSphere deployment tool. The deployment tool for
WebSphere 4.0 differs depending on the version of the server you are using. For the
Single Server, WebSphere’s deployment tool is SEAppInstaller. For the Advanced
Edition, the deployment tool is XmlConfig. Therefore, the appearance of the Deploy
Settings dialog box will vary between these two WebSphere Server 4.0 editions.
If your target application server is WebSphere 4.0 Advanced Edition and you want an
XML file to be generated as input to the WebSphere XMLConfig utility, check the
Generate XML check box. If this option isn’t checked, the file won’t be created. If you
make your own modifications to the generated XML file (named
deploy_<selectednode>.xml and appearing under the EJB module node or EAR group),
uncheck this option to be sure you don’t lose your changes. If you use the Deployment
Options on the context menu (right-click the EJB module and choose Deployment
Options <jar name>.jar to see the deployment commands), the generated XML file is
deploy.xml. It appears under the project node.
Remote deploying
Follow these steps to use the WebSphere Deploy Settings dialog box to deploy to a
remote server:
1 Choose Enterprise|Server Deployment.
2 Select the Deploy action.
3 Specify these options in the Options field:
-nameServiceHost<host name> -nameServicePort<port number>
4 Set the Primary Node and Server Name to match your server configuration.
5 Click OK.