Overview of Pramati Studio

Pramati Studio is a server-side integrated development environment that is designed for enterprise Java application developers who wish to create, assemble, run and debug Java 2 platform, Enterprise Edition (J2EE) applications.

It provides tools, wizards and templates for developers who wish to move quickly into the J2EE space. Studio gives control over a component's complete development lifecycle and allows developers to configure the toolsets to suit their particular environment.

The following are some of the important tools and features in Studio, which enhance the productivity of users.

Enterprise Editor

The Editor enables power-users to effectively work with JSP Pages, Servlets, EJBs, Java files, HTML files, and XML files. Use the following coding features to simplify code typing and navigation:

Code completion with QuiCode

Browse classes, variables and methods with Source Code Browsing.

Auto indexing of sources generated in Studio

Abbreviations to introduce common constructs in a few keystrokes

Power features like- block commenting and uncommenting, import completions, extends lists, and implements lists

Color-coding support for all J2EE files

EJB, JSP, Servlet and Filter Templates

Create customized, ready-to-code EJB, JSP, Servlet and Filter templates that can be edited to add copyrights and custom code, and change tracking and logging information.

Bean Wizard

A powerful template-based wizard that walks you through all the steps to define complex EJB 1.1 and EJB 2.0 compliant beans, including MDBs. The bean wizard generates Java sources (bean skeleton, PK classes and home, remote, local home, local interfaces) leaving only the business methods to be written.

Bean Wizard supports Session Synchronization, Re-entrant beans and multiple EJB-names. It supports all Container Managed Relationships and Container Managed Fields under EJB 2.0.

Auto-generate bean skeletons for Session and Entity beans with CMP/BMP for both EJB 1.1 and EJB 2.0

Define and expose business methods on appropriate interfaces

Define CMRs for all types of cardinality (one/many), directionality (uni/bi) as well as various return types

Interface Wizard

Eliminate coding errors and effort in creating standard interfaces. The Interface Wizard generates all interfaces for EJBs, appropriately exposing selected methods.

Query Designer

A wizard to create queries based on your database schema for EJB 1.1 applications. Support for EJB QL for EJB 2.0 applications. All queries are transparently embedded in the packaging XML.

Create queries using the Query Wizard for entity beans

Pramati Studio converts generated SQL queries to application server-specific formats (e.g. to WLQL) for transparent migration of applications across servers

Specify queries in EJB QL for EJB 2.0 CMP beans

Resource Tool

An easy to use interface to define and manage multiple types of application resources like database, messages, URLs, Connectors and Mail.

Define database resource and connection pool in terms of JNDI name of the resource, JDBC driver, URL, user name, password

Define XA data resources that allow two-phase commit in transactions (part of the JDBC 2.0 Standard Extension)

Define JMS Resource like Destinations and Connection Factories to use Asynchronous Messaging through a JMS Server

Define Java Connector API (JCA) Connection Factories to connect to non-J2EE applications using the Resource Adapter Archives (RAR) available on the Server

Define mail resource for using the JavaMail API

User Manager

Build JAAS-based security models into your applications. The JAAS API allows creation of a portable policy-based security model (using the XML Security Realm for testing purposes). Secured components can then be deployed on any configured server with any realm (including LDAP, DB and shared file systems).

User Manager enables definition of users and groups which are then mapped to application roles during deployment. Users and groups are defined transparently on all configured servers.

Package Tool

Create standard, portable packaged archives that can be deployed on any application server. Package Web components into Web Archives (WARs conforming with Servlet 2.3 and JSP 1.2 standards), and EJB JARs into Enterprise Archives (EAR conforming with EJB 2.0 standards). The Package Tool hides the underlying complexity involved in coding the mandated XMLs through simple, graphic interfaces. To reduce round trips to packaged components, modified sub-components can be reflected in archives with a single click.

Package EJB 2.0 beans according to the EJB 2.0 CMR graphs, to maintain the consistency of the JAR with validation to identify bean types.

Extend the tool by using the packaging API.

Deploy Tool

Abstract away vendor-specific deployment descriptors and processes for all configured application servers through a single, intelligent tool. The tool reads target server environment properties and resolves references of EJBs at deploy time. Enables smart O-R mapping using DB constraints for EJB 2.0 relationships.

Complete O-R mapping and other deployment information through the deploy tool.

Automatic O-R mapping for relationships by inspecting the constraints in databases.

Generate the SQL code on a database needed for deploying beans along with all the constraints.

Manage unfinished tasks with an intelligent task manager that displays list of incomplete tasks

J2EE Application Debugger

Seamlessly move between JSP Pages and EJB methods. Use a smart method to alter the behavior of debug step modes (into, over and out) through the source. Debugger provides special handlers to investigate values in collections, maps and arrays.

Debug JSP Pages at the script level, not as Servlets

Debug applications running on multiple and remote servers

Feed values to variables and watch results at runtime

Pick up source files dynamically

Set conditional breakpoints

Drill down variables as code executes

Migration Tool

Support any J2EE server with the same code base. Move rapidly to pure J2EE from any other development environments and deployment platforms with the powerful Migration Tool.

Migrate raw sources

Migrate packaged archives

Migrate deployable archives from other servers with package and deployment XML descriptors

Generate Migration readiness report to analyse and remove all server-specific lock-ins

Convert sources into a Studio Desk with only source hierarchy, Desk having modules with package XMLs, Deployable Desk with all deployment descriptors

Express Development

Express Development automates tasks in a typical J2EE development lifecycle. It allows a developer to deploy applications without getting trapped in complex J2EE development cycles.

Express Development collapses the four step process of Create-Assemble-Deploy-Run to the two step Create-Run process. Developers can just code and run the J2EE application, while Express Development

Auto-generates Interfaces

Auto-compiles Interfaces

Auto-packages components

Auto-update archives

Developing on Multiple Application Servers

Insure past investments in J2EE by maintaining a common code base for multiple application servers. Pure J2EE code with no proprietary extensions.

Studio is completely application server neutral. While it has an in-built J2EE server, it also enables deploying on any other standards compliant application server.

Studio can be configured to work with multiple application servers. The developer needs to enter the deployment descriptors only once through a common and intuitive UI for all servers. Studio synchronizes descriptors as bean sources change.

Studio provides in-built containers for test-deploying EJB 1.1 and EJB 2.0 components. Studio provides tools to seamlessly test deploy on the following servers:

Pramati Server 3.0

WebLogic Server 6.1, 6.1 SP1, 6.1 SP2 and 7.0

WebSphere 4.0 and

Oracle 9iAS

Version Control System

Studio provides Open API to plug-in any version control system, and provides out-of the-box integration with CVS. Studio Desk is sensitive to the version of files, and ensures source code integrity during development. Modified files are highlighted along with their package hierarchy. Standard functions like Checkout, Checkin, Update, Commit, Add, Differences, Log, Status and Remove, are available in Studio.

Creating Custom Tools with Open API

Studio is designed as an Open API into which Studio native tools are plugged in. The framework exposes this multi-tiered API to power users who may wish to extend the IDE through specialized, custom tools that further enhance productivity in a particular business domain. These custom tools are plugged in using stitch classes as prescribed in the API.

Application infrastructure providers can customize the framework in order to empower customers to create applications on their infrastructure.

Quick Tour

Menu bar

Tool bar

Status bar

Framework panels: Display, Explore, Output

The tool bars and menu bars can be configured by adding or removing tool and menu items.

Menu bar

Menu bar contains default menu items and menu items that are attached to it by the tools that are deployed on the framework. The default menu items are File, Desk, Edit, Search, Build, Tools, Debug, View, and Help.

Tool bar

The Tool bar contains buttons and components for tools deployed on the framework.

The Build tool attaches compile and compile all buttons and the Editor attaches the Find combo box to the tool bar.

Status bar

Message box displays help messages.

Row/Col box displays the position of the cursor in the editor.

Server box displays all the Servers instances that have been configured in Studio. Select the required Server instance from the Server box and deploy the applications on it. By default, the Server box displays only the in-built Pramati Server.

Signal box displays the current status of the built-in test Server. The green button is highlighted when the Server is running and the red button when the Server is stopped. These buttons can also be used to start and stop the Server.

Viewing Menu Options

View Full Screen

Click on View > Full Screen to switch between the full-screen view and normal view. Only the Display panel can be seen in the full-screen view.

View Explore Panel

Click on View > Explorer to view the Explore Panel. By default this view is checked.

View Output Panel

Click on View > Output to view the Output Panel. By default this view is checked.

View Toolbars

Click on View > Toolbars and add or remove the following toolbars by checking or un-checking them:

Standard

Any other user configured

View Output Tabs

Click on View > Output Tabs and check/uncheck the following options to add/remove the corresponding output tabs:

Build

Express Development

CVS

To hide all the tabs in the Output Panel, click on View > Output Tabs > Hide All. This hides the Output Panel from being viewed.

To view all the tabs in the Output Panel, click on View > Output Tabs > Show All.