This is a feature of JBuilder Enterprise.
The EAR Group Properties dialog box allows you to modify the attributes of an EAR group.
To display this dialog box, right-click an EAR group node in the project pane.
The Build page allows you to specify attributes about an EAR group created with the EAR wizard.
The Build page always contains an EAR page and a Resource page.
The name of the EAR file that is produced when you choose to Make or Build the EAR group.
The name of the JAR file. JBuilder suggests a default name based on the name of the EJB module, but you can change it.
The path where the JAR file is created.
Lists the .xml
deployment descriptor files that are in the EAR group.
Use Add to add an existing deployment descriptor into the list of files in the EAR group.
Use Copy to copy the selected deployment descriptor to a new location.
Use Delete to remove the selected deployment descriptor from the list of files in the EAR group.
Use these options when you want a copy of the your current deployment descriptors made each time you save the EAR group or project. Developers who write their own build tasks might find this capability desirable.
Check this option if you want the descriptors copied to the directory specified in the Directory field each time you save the EAR group or the project.
Specify the directory where you want the deployment descriptors saved.
By default, an EAR is always created during the build process. Uncheck this option if you want to defer creating an EAR.
JBuilder copies all known resource types from the source path to the output path during the compile process. By default, JBuilder recognizes all images, sound, and properties files as resources and copies them to the output path. You can override these default resource definitions on individual files or by file extension project wide. See "Setting the output path" for more information on the output path.
The top three radio buttons are file-specific options that control the currently selected file(s). These are the options:
The Copy and Do Not Copy options select an absolute behavior: always copy to the output path or never copy to the output path when the project is built, regardless of whether or not the file type is considered a resource.
The third option, Use File Extension Defaults, allows JBuilder to decide whether to deploy the file based on its file extension in the file list below. This is the default behavior for all newly created files and files in existing projects. The correct extensions for the selected files are automatically selected in the list to highlight the default behavior.
Important: If the selected files or extensions do not all share the same setting, none of the radio buttons in the corresponding group are selected. Selecting one of the radio buttons changes everything to the same value, while leaving none selected allows the differing values to be left alone.
If you have changed the defaults for individual files and you want to return them to JBuilder's defaults, select the files again and choose Use File Extension Defaults.
Below the three file-specific options is a list of all known file extensions and their default deployment behavior. These defaults can now be changed on a project-by-project basis. Select one or more extensions and use the radio buttons on the right to change the default behavior for these extensions in the current project. These options include:
Use the Reset button to return all files in the file extension list to the state they were in when the dialog box was displayed. Remember, this does not change your individual file settings to the default.
This is a feature of JBuilder Enterprise.
Use this page to specify the EJB modules containing the enterprise beans and any other JAR files you want to include in this EAR file. For information about EJB modules, see "Creating EJB 2.0 components with JBuilder"
Click the EJB Modules tab and from the list of available EJB modules in your current project, check the check box next to those you want to include in the EAR file.
To add JAR files for enterprise beans that aren't in an EJB module in the current project, click the External JAR Files tab, click the Add button, and navigate to the location of the EJB JAR files you want included. As you add JAR files, the list of External JAR Files grows.
This is a feature of JBuilder Enterprise.
Use this page to specify the Resource Adapter Archive (RAR) files you want to include in this EAR file. For information about RAR files, see "About Resource Adapters" in Sun's J2EE Tutorial at http://java.sun.com/j2ee/tutorial/doc/Connector2.htm.
Click the RAR Archive Nodes tab and from the list of available RAR archive nodes in your current project, check the check box next to those you want to include in the EAR file.
To add external RAR files to the current project, click the External RAR Files, click the Add button and navigate to the location of the resource adapter archives you want included. As you add RAR files, the list of External RAR Files grows.
This is a feature of JBuilder Enterprise.
Use this page to specify the J2EE application client JAR files you want to include in this EAR file.
Click the JAR Archive Nodes tab and from the list of available JAR nodes for J2EE client applications in your current project, check the check box next to those you want to include in the EAR file.
To add external J2EE client application JAR files to the current project, click the External JAR Files tab, click the Add button and navigate to the location of the JAR files you want included. As you add JAR files, the list of External JAR Files grows.
This is a feature of JBuilder Enterprise.
Use this page to specify the WebApp nodes and any external Web Archive (WAR) files you want to include in this EAR file. For information about WebApps and WAR files, see "Working with WebApps and WAR files."
You must specify a different context name for each web module, whether the module is from a WebApp node or from an external WAR file. One blank context name is allowed. The blank web module becomes the default web context for the enterprise application.
Click the WebApps Nodes tab and, from the list of available WebApp nodes in your current project, check the check box next to those you want to include in the EAR file. When you check the check box, a default context name appears. You can edit this context name if you choose.
To add external WAR files to the current project, click the External WAR Files tab, click the Add button, and navigate to the location of the WAR files you want included. As you add WAR files, the list of External WAR Files grows.
This is a feature of JBuilder Enterprise.
Use this page to add any other files you want to add to the resulting EAR group. The file can be of any type, including non-J2EE types.
Click the Add button to display the Select One Or More Files dialog box and use the dialog box to specify the file you want to add. Continue adding files until you've specified all the files you want to add.
To remove a file from the EAR group, select the row in the grid containing the file name and click Remove.
This is a feature of JBuilder Enterprise.
The EAR Group Properties page includes a Deployment page for those servers that can deploy an EAR group.
The information on the Deployment page differs depending on which server is your selected server for your current project.
Use this page to specify parameters to send to the Java Virtual Machine.
The parameters you want sent to the virtual machine. The default parameters are these:
-Dvbroker.agent.port=42424 -Dvbroker.security.disable=true
For more information about parameters you can specify, see the Borland Enterprise Server documentation.
Check this option if you want your project output path to become part of generated command line.
Check this option if you want your project libraries to become part of the generated command line.
Use this page to specify parameters to send to the Java Virtual Machine.
Specify the host name.
Specify the container name.
Specify the parameters you want sent to the virtual machine.
Check this option if you want your project output path to become part of generated command line.
Check this option if you want your project libraries to become part of the generated command line.
Consult your Borland AppServer 4.5 documentation for information about parameters you can specify.
Use this page to specify deployment options for WebLogic 6servers. Consult your WebLogic documentation for information about what to enter in these fields.
The Admin URL.
The name of the server to which you are deploying.
Your user name.
Your password to log on to the server.
Specify the name of the unit your are deploying. This is likely to be the name of the EJB module.
Deployment options.
The parameters you want to pass to the virtual machine.
Check this option if you want your project output path to become part of generated command line.
Check this option if you want your project libraries to become part of the generated command line.
Use this page to specify deployment options for WebSphere 4.0 Single Server. Consult your WebSphere documentation for information about what to enter in these fields.
Specify the types running in the container you want to see listed.
The name of the primary node.
The name of the server to which you are deploying.
Specify deployment options.
The parameters to pass to the virtual machine.
Use this page to specify deployment options for WebSphere Server 4.0 Advanced Edition. Consult your WebSphere documentation for information about what to enter in these fields.
The name of the primary node.
The name of the server to which you are deploying.
The name of the container.
Specify deployment options.
The parameters to pass to the virtual machine.
The remote location of the archive you are deploying.
The home directory of the remote server.
Generates an XML file for input to the XMLConfig utility. Check this check box when you want to generate the XML file and then modify it. When generated, the file appears under the EJB module node in the project pane. If you then want to test your modifications, you should then uncheck this option so that the XML file is not overwritten.
Check this option if you want your project output path to become part of generated command line.
Check this option if you want your project libraries to become part of the generated command line.
Use this page to specify deployment options for the iPlanet Application Server 6.x+. Consult your iPlanet documentation for information about what to enter in these fields.
Specifies that the module deploys to a local server.
Specifies that the module deploys to a remote host. You must specify the following settings.
The name of the host or the IP address.
The port used to communicate with the host.
Enter a user name to connect with the host.
Enter a password to connect with the host.