Working with Pramati Enterprise Server

Developers familiar with Pramati Enterprise Server can test deploy their applications on Pramati Enterprise Server via Studio. Studio provides tight integration with Pramati Enterprise Server. The required deployment descriptors are automatically created while the application is being developed, and the application kept in a "ready-to-deploy" state.

Select Tools > Configure from the main menu.

In the Configure panel, select Pramati Enterprise Server from the Available Tools section.

Click Close.

Creating Enterprise Server Instances

Select Tool > Server Configuration from the main menu.

In the Server Configuration dialog, click New to create a new instance of the server.

In the Add New Server dialog, enter the name of the server instance to be created and select the type of the server from the dropdown as Pramati Enterprise Server.

Press OK to create a Server instance. In the Server Configuration panel, configure Enterprise Server properties.

Server Name: Selected as the name entered in the Add New Server dialog, automatically. To select another server instance, use the dropdown

Server Type: Displayed as the type selected in the Add New Server dialog

IP Address: The machine address where the server has to be configured. The default value is 127.0.0.1 or localhost

Naming Port: Port on which the Server will listens. Default value is 9191

HTTP Port: Port on which the Web server listens. Default value is 8181

User Name: Enter the valid user name required to start the remote server. The default value is root

Password: Enter the password of the specific user. Default value is pramati

Realm: The realm to which the Server is assigned. D efault value is system

Click OK to add the configured Enterprise Server instance. Click Delete to delete an instance.

Working with Enterprise Server from Studio

Select the Enterprise Server instance from the Server Box in the Status bar to make it the current server. All server specific operations for the active desk is performed on the current server.

The Enterprise Server cannot be started or stopped from Studio and applications are not added transparently. Ensure that details such as database resources, users, and groups are present in the Enterprise Server container before deploying the applications.

Applications can be deployed on the Enterprise Server as JARs, WARs and EARs, or directly as modules. Right Clicking on the Desk > Deploy always deploys the application on the current Enterprise Server. Similarly right clicking on the module/Desk root node > Deploy always deploys it on the current Enterprise server. A progress bar displays the deployment progress.

Note: There are no deployment messages displayed in the server output panel to indicate success or failure of the deployment. This will be included in a later version of Studio.

All the command line options of the remote shell can be performed in Studio for the Enterprise Server instance. For example, type list in the Server Output tab and view the state of the application. To shut down the server, type shutdown.