|
|
Studio ships with an in-built Pramati Server, which is J2EE 1.3 certified and needs no set up and configuration. The in-built Pramati Server allows each developer to independently build and debug J2EE components before integrating them with the project.
This chapter is for developers who are familiar with Pramati Server, and would like to test-deploy their applications using the same.
Studio automatically creates the required deployment descriptors while the application is being developed, and keeps the application in a "ready-to-deploy" state. It also creates connection pool, data-source, mail resource, Connection factories, topics, and queues on the server. This chapter discusses how to develop EJB 1.1 and EJB 2.0 applications using Studio and then deploy them on the in-built Server.
Note: Each configured Server instance has its own tab in the Output Panel.
The in-built Pramati Server is configured in Studio by default. To make any changes in the default settings, go to Tools > Server Configuration. This opens the Server Configuration panel. Enter the following data.
Server Name The name of the server is displayed in this field. The server selected by default is In-Built. Selecting the specific server in this field displays the other related fields in the panel.
Server Type The type of Server is Pramati In-Built Server 3.0. This field is non-editable.
IP Address This is the IP address of the machine on which the In-Built Server is installed and where the application will be deployed. The value is 127.0.0.1, and cannot be modified.
Naming Port Port on which the Server listens. The naming port value is 9191. This field cannot be edited.
HTTP Port Port on which the Web server listens. The HTTP port value is 8181. This field cannot be edited.
User Name The valid user name required to start the remote server. The default value is root, and cannot be modified.
Password The password of the specific user is displayed here. The default value is pramati and cannot be modified.
Realm The realm to which the Server is assigned. The default value is system, and cannot be edited.
Server Classpath The server classpath added here applies only to the active Desk. Therefore the classpath needs to be set for each Desk separately.
Use the button with the plus icon to add the application utility JARs to the Server classpath. These JARs get appended to the server's classpath. To move the JAR added up or down, use the buttons with the up or down arrow icons.
JVM Options Enter or browse through the standard Java options provided, using the browse button. These options are used to start the server. No default value is provided.
Example
-Xms 64m, -Xms 128m
Command Line Options Enter or browse through the command line options used to start the Server, start the deploy tool, or deploy and start/stop ready-to-run JAR, WAR and EAR.
Example
-startapps,-keep,-nojms
Trace Level Choose from the options available to generate the Server tracing information during Server execution.
Start JMS Server Use this checkbox to start the JMS Server with the default Pramati Server 3.0. The checkbox is by default, unchecked.
Use Inprocess javac This option is by default checked. It makes deployment fast. In case of large applications, uncheck the option as you may encounter the Out of Memory error.
Use Inprocess rmic This option is also checked, by default. It makes deployment faster. In case of large applications, uncheck the option as you may encounter the Out of Memory error.
Use the OK button to apply the changes. To delete a server instance, select the required server from the field, Server Name and use the Delete button.
Starting/ Stopping Server
By default, the Server box (in the Status Bar) displays only the in-built Pramati Server, and all applications are deployed on this. Use Tools > Start Server to start the Server, and Tools > Stop Server to stop the server. The Server can also be started/stopped using the signal box.
Applications can be deployed on Pramati Server as normal archived JARs, WARs, and EARs, or directly as the Desk tree nodes and modules. Directly deploying from the Desk tree nodes and modules uses the Express Development feature provided by Studio.
Studio ships with an in-built Pramati Server, and all applications are by default deployed using the in-built server.
Right Clicking on the Desk > Deploy/Deploy as .ear always deploys the application on the in-built Pramati Server. Similarly right clicking on the module > Deploy always deploys the module on the in-built Pramati Server.
Note: For deploying entity beans with container managed relationships on Pramati Server, ensure that there are database constraints between the tables, which they map to.
Applications deployed on Pramati Server can be debugged in Studio, using the Debugger tool. Applications can be debugged normally, conditionally and remotely. JSP Debugging assumes that the application has been deployed on the in-built Pramati Server.
| Pramati Technologies © Copyright |
   
|