|
|
After creating the Web and Java archives (WARs and JARs), which hold the web and the EJB components, you can package all the component archive files into a single, deployable enterprise application unit. To enable these components in the web and Java archives in collaborating and making the enterprise application run, you should package the two archives into a single Enterprise Archive (EAR). The EAR has its own deployment descriptor, which is stored in a XML format.
Tools > Package > EAR > Add JAR/WAR
Clicking the Add JAR button displays a list of all the JAR files in the active Desk. Multiple JARs can then be selected and added to the EAR at the same time.
Clicking the Add WAR button, prompts you for a WAR file and the context root for the WAR.
You can add JARs and WARs that are present in the active Desk. To add an "external" JAR/WAR to the EAR, you should first import it on to the Desk.
Tools > Package > EAR > Select The Row > Delete
You can delete the JARs and WARs in the EARs by selecting any row in the table and deleting the same. Here the row signifies a .jar file or a .war file.
Tools > Package > EAR > Add RAR
Clicking the Add RAR button displays a list of all the rar files in the active Desk, that were imported from outside Studio. Multiple RARs can then be selected and added to the EAR at the same time. RARs in Studio can be deployed only once they have been added to an EAR.
There are two ways of updating an EAR.
Ear file on the Desk > Right Click > Update
Updates the JARs and WARs individually, and then adds the updated JARs and WARs to the EAR. For the Tool to find the correct JARs and WARs, information about their location is stored in update.props inside the EAR.
All the deployment time information in the bean properties panel are not picked up when updating the EAR.
If the information found in update.props is not correct, a log of update operations is available on the Update Tab in the Output area of Studio. This log shows normal messages in black, updating messages in green and any failures or errors in red. Usually a remedial measure is also provided in the case of errors. A progress bar indicates the progress of the operation.
Choosing Update brings up a dialog box with a progress bar. All the updating messages are displayed here. To stop updating the EAR, click on Cancel.
Studio in the meantime can be used as usual but the EAR file being updated cannot be opened. The JARs and WARs being added to the EAR should not be opened.
EAR file on the Desk> Right Click > Quick Update
A time stamp based update of the EARs looks for the time stamp of the JARs and WARs and adds them to the EAR if they are different. Update your JARs and WARs before using Quick Update on the EAR.
Choosing Quick Update brings up a dialog box with a progress bar. All the updating messages are displayed here. To stop updating the EAR, click on Cancel. Studio in the meantime can be used as usual but the EAR file being updated cannot be opened. The JARs and WARs being added to the EAR should not be opened. If the package names of the above are changed, then the EAR is not updated.
For the Tool to find the correct JARs and WARs, information about their location is stored in update.props inside the EAR. If the information found in update.props is not correct, a log of update operations is available on the Update Tab in the Output area of Studio. This log shows normal messages in black, updating messages in green and any failures or errors in red. Usually a remedial measure is also provided in the case of errors. A progress bar indicates the progress of the operation.
A Quick Update is generally used when one JSP or bean has been changed in a single JAR or WAR. These JARs and WARs should be updated before using Quick Update on the EAR.
Tools > Package > Ear > Save
Saves the open EAR.
Tools > Package > Ear > Close
This command closes the current EAR. If the EAR is not saved, it is saved.
Tools > Package > EAR > Revert
The EAR can be restored to its last saved state.
The application.xml file corresponding to the EAR file can be viewed in the XML node.
Relocate queries.props file along with the EARs when deploying an application in another location.
| Pramati Technologies © Copyright |
   
|