REFERENCE:
Working with the Expert, you should describe what's to be done. Each page of the Expert contains a number of tasks. After you have entered all necessary fields, and pressed Finish button, the Expert starts executing the selected tasks. This topic provides explanations of the available tasks. Most of the tasks (with some exceptions) can be executed separately.
Add libraries, required for deployment, to the project Search/Classpath
EJB deployment requires a number of server specific libraries. Since diverse servers use specific versions of J2EE specification, they generally suggest their own libraries that cover J2EE specification for the particular server usage. Therefore, server specific library is normally added to the Classpath instead of Sun J2EE. Check this box to compile and deploy EJB or client program, and to make sure that you have all required libraries on your Classpath.
Verify/Correct EJB source for compliance with WLS 5.1 requirements
This task verifies that the classes on the current diagram correspond to EJB specification supported by the destination server. Moreover, some servers have individual specification features. The primary objective of this task is to make sure that all the required classes exist on the diagram.
Note: The current diagram is used as the source of beans. Therefore, you have to open appropriate class or assembler diagram.
Compile classes from selected diagram
Compiles the bean and packs it to a JAR file. New archive is stored in a temporary folder. Standard Sun tool (javac.exe and jar.exe) is used for compilation and packing.
Generate deployment descriptor / Open XML Editor for generated DD
Generates deployment descriptor and opens XML Editor, where you can edit it. Two additional descriptors are generated, one for each CMP entity bean. As soon as the descriptors are ready, they are added to the JAR archive together with some additional classes. WebLogic ejbc.exe tool is responsible for these operations, which results in a JAR file ready for deployment.
Create Database Table for CMP EJB
Defines a repository where CMP EJB will be stored. See bean speedmenu (Entity EJB tab | Db binding subtab). The current task automatically creates tables required for bean persistence. Check this box if the table is missing in the database.
Hot Deploy (use "Start Weblogic Application Server 5.1" or start the server manually)
If you check this box, deployment will be executed. This step makes use of a bean already compiled and jarred. Therefore you have to use this step in conjunction with the others.
Warning: Be aware that all hot deployed beans will be lost after WebLogic termination. You will have to re-deploy necessary beans again. In order to deploy your beans permanently, you have to add certain lines to weblogic.property file manually.
Note: As a rule, it is strongly advised to compile classes, generate descriptiors and deploy the beans all together, because some tasks use the results of the previous tasks. For example, Hot Deploy task requires *.jar file to be prepared in a temporary folder.
Process Servlet(s)
Check this box to compile servlets, if they exist on the current diagram. Automatic server deployment is not provided. As of this writing, you have to deploy your servlets manually.
Generate simple JSP client
Check this box to generate a JSP client for the Enterprise Beans. Client is a set of interrelated JSP and HTML files, which can be viewed in any Internet browser. The intention of this client is to demonstrate access to remote EJB objects through the opened interfaces. The semantic information required for JSP client generation is taken from the active diagram of the current project . Due to the lack of information, it is impossible to create a client program ready for commercial use. That's why JSP client can be regarded as a universal testing facility.
Clear temp folder before start / Clear temp folder after finish
Skip these tasks if you want to reuse temporary files.
The fields on this page are quite self-explanatory. However, this section provides brief descriptions for some of them .
Folder for the generated JAR file
Specify location where the resulting JAR file will be stored and from where it will be loaded by WebLogic.
Short name of EJB JAR file
This name is assigned to the JAR file generated in Compile Classes task from the selected diagram. While preparing for deployment, an additional JAR file is created, whose name is based on the short name assigned here.
On this page you can select whether deployment will stop if verification fails, correct the source code to comply with the requirements of WebLogic 5.1 specification, and create backup copy of the source code... just in case.
This page enables assigning properties required for the Hot deploy task.
System password
System password is defined in course of the WebLogic installation.
Server port
Default server port is 7001. If you don't know the server port number, you can find it in weblogic.property file.
Server host
As a rule, the server host is assigned to localhost,since this deployment expert uses the file system access to WebLogic server, and therefore the server runs on the same computer.
Before proceeding to the next page, make sure that the server is available at the selected port and host.
This page shows up if you have checked appropriate flag on the first page of the Expert and contains entries for the properties required to generate a Simple JSP client.
The fields are quite self-explanatory.
Weblogic public directory
This directory is the root of the file hierarchy, which can be accessed from outside. Thus, if you want to allow access to some HTML of JSP files, you have to place them here. By default, Weblogic public directory resides at [Weblogic home]/myserver/public_html.
Subdirectory for placing JSP files
To avoid disorder in the public directory it is advisable to group the files in a subdirectory. Enter path to the subdirectory where your files will be stored. This path is relative to the root public directory. If the subdirectory does not exist, it is created automatically (after confirmation).
Base URL for browsing JSP
In order to browse a remote WEB resource, we have to set its URL. Standard web URL includes protocol, host, port, web resource alias, and path. Specify all parts of the URL, except for the path. During request processing, the server substitutes this base URL to WebLogic public directory in order to access the requested web resource. Wrong value of this field or WebLogic public directory causes access error. By default base URL is http://localhost:7001/.
Show result after generation
Check this box to launch your default Internet browser and display the start page.