...
To facilitate the creation of deployment plans there is a new portlet now available. The plan creator Plan Creator wizard available from the Geronimo Administration Console makes deployment easier by asking you some questions and proposing default values when providing a web application walking you through a sequence of steps to auto-generate the geronimo-web.xml for a given WAR file.
Supported features
The plan creator wizard will help you generate the appropriate deployment plan for the application you are deploying. The wizard currently works for web apps and supports the following features.
- References: EJB, EJB Local, JDBC Connection Pool, JMS Connection Factory, JMS Destination, JavaMail Session & Web Service References references declared in the web-apps are auto discovered and users are asked to resolve them by listing Available Resources in the server environment to which they can be linked.
- Above type of references declared inside the Java classes through Annotations are also auto discovered.
- Simplified configuration of Security.
The plan creator wizard will behave differently depending on the type of application you are installing. The following sections provide sample applications with different features so you can better appreciate the wizard behavior.
Sample with annotations
There are three four simple applications attached to give you a better idea of how the plan creator wizard would work when deploying web applications using annotations.
- JDBC access
- EJB access
- JMS access
- Security access
JDBC access
Anchor | ||||
---|---|---|---|---|
|
...
The Annotations-TestJDBCAccess.zip file provides a BankDB.sql
, WebAppJDBCAccessAnnotations.war
which is the WAR we will be deploying and a sample of the generated deployment plan WebAppJDBCAccessAnnotations_generatedPlan.xml
. Download and extract the zip file to a directory of your convenience.
WebAppJDBCAccessAnnotations.war
includes a Servlet and a JSP. The following excerpt shows the annotation part the wizard has identified and will likely be prompting for additional information while deploying the application.
...
In the following screen, the wizard would have identified some all WAR references that need to be resolved. The references listed on this screen are specific to this application. The JDBCRef column is showing the resource name defined in ListCustomers.java
; see *@Resource(name = "jdbc/MyDataSource")
from the excerpt above.
...
The Annotations-TestEJBAccess.zip file provides the CurrencyConverterEJB.jar
that needs to be deployed first, the WebAppEjbAccessAnnotations.war
which is the WAR we will be deploying and a sample of the generated deployment plan WebAppEjbAccessAnnotations_generatedPlan.xml
. Download and extract the zip file to a directory of your convenience.
...
On the Archive: field browse to the CurrencyConverterEJB.jar
file you just extracted and click "Install", this will install and start the JAR. You can verify the status of this JAR by clicking on EJB JARs link from the menu on the left. It should display something like this:
No Format | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Component Name State
default/CurrencyConverterEJB/1199743733609/jar running
|
WebAppEjbAccessAnnotations.war
includes a Servlet and a JSP. The following excerpt shows the annotation part the wizard has identified and will likely be prompting for additional information while deploying the application....
In the following screen, the wizard would have identified some all WAR references that need to be resolved. The references listed on this screen are specific to this application. The EJBRef column is showing the resource name defined in ConverterHandler.java
; see *@EJB(name = "ejb/Converter")
from the excerpt above.
From the EJBs Deployed pull-down menu select the JAR you deployed earlier ConverterBean (default/CurrencyConverterEJB/1199743733609/jar)
and click Next.
The following screen list all available modules and allows you specify additional modules this WAR has dependencies on. This screen also provides a default selection, in this case the EJB JAR you deployed previously will be already selected. Accept the default and click Next. For most scenarios the default values should be sufficient.
...