|
|||
| ipas 3.0 plugin > documentation | |||
|
This is the documentation for the iPAS 3.0 Eclipse plugin. To setup the plugin please read the configuration guide. iPAS Plugin Functionality
The plugin integrates the tools you know from the iPAS tool console into eclipse. Have a look at the screenshots and you see the supported functionality.
Screenshot showing the toolbar elements of the iPAS plugin
Screenshot showing the menu entries of the iPAS plugin The plugin contains sofisticated support for IONA's EARSCO structure. Each EARSCO structure is mapped to a Java project. Each EARSCO src directory is mapped to a Java src directory of the Java project. Create EARSCO based Java project There is a special Java project wizard that allows you directly to create a Java project with EARSCO support. If you create a EARSCO based Java project then the EARSCO structure is set up and a application.xml and cc.xml file are added.
New project wizards with iPAS Wizards
Convert an existing Java project into an
EARSCO based Java project If you have an existing Java project then you can add EARSCO support using this tool. The directory structure will be set up and the application.xml and cc.xml files added if necessary. Add EJBs, WARs to your EARSCO structure
This menu will start the EARSCO Administer tool that allows you to add, modify or delete EJBs, clients or WAR files from your EARSCO structure. Build, Clean Perform a Build or Build Clean operation on the EARSCO structure. The Build operation is by default done using the -r option (regenerate the earbuild.xml). If you have problems with the Build operation check that you have the javac in your system path and the tools.jar of your JDK in the classpath of the "IONA IPas" project. See configuration for details. You can start the iPAS in the run or debug mode. The debug mode allows the debugging of your EJBs. This tools allow you to deploy and undeploy EJBs. The wizards known from the iPAS tool console will be started. If you select an ear in the packages view of the Java perspective then you will get in the context sensitve menu (right click) menu entries for deploying the EAR and starting a client contained in the selected EAR (see screenshot). You can start the client either in debug or run mode. The client will be started using the iportal.client helper class.
Screenshot showing the EAR context menu By default the cc.xml file is used as container configuration to deploy the EAR. You can specify another file containing the container configuration in the properties view of the EAR file.
Screenshot showing the properties view of the EAR file Start iPAS clients without iportal.client If you want to start an iPAS client without the iportal.client option (maybe you have a simple jar containing your EJBs) then you can use the IPas Launcher. This launcher sets the system properties needed for the iPAS (see iPAS documentation) and uses the classpath defined by the "IONA IPas" project.
Screenshot showing the IPas Launcher This tool starts the Assembler known from the iPAS tools. See the iPAS documentation for additional details. General Configuration Issues Defining the iPAS server name If you have an iPAS server other than the default one, you can configure its name in the iPAS Eclipse preferences. See configuration for details. This name will be used (using the -n option) for starting iPAS, stopping iPAS and the tools. iPAS configuration The location of the loaded iPAS configuration is defined through the classpath of the Java project "IONA IPas" defining the classpath for the iPAS and its tools. |
|||
|
(c) 2002 X-Parrots, last update Feb
6, 2002
|
|||