Product Line Studio uses a 3-tier architecture consisting of the Client Tier, the Integration Server Tier, and the Data Persistence Tier.

Client Tier

The client tier uses a Java Swing-based GUI client application, employing a network connection with the Integration Server (middle tier).

The client is deployed using Java Web Start technology, which gives zero-administration on the client.  There is never a need for an administrator to touch each client computer, and each client is always up to date with the correct version of the client application.

The client / server interface uses coarse-grained batching of requests, giving it good performance over slow network connections which would cause many client / server systems to be unusable. PLS can be used on a WAN with a single server installation. Under ordinary circumstances, PLS is even usable over a dial-up modem connection!  In general, a PLS connection can be used wherever a simple HTML web application can be used.

Last, the client application operates on Microsoft Windows, Apple OS X, and Linux. Additionally PLS supports connection tunneling via SSL to support secure connection from clients outside the corporate firewall.

Integration Server Tier

The Integration Server Tier is where the essential business logic resides. It is implemented as a set of stateless services.  All data access goes through the Integration Server, giving it the ability to enforce policies (access control, change policy, approval policy, etc.)

The integration server implements all integrations with 3rd party tools such as a defect tracker (e.g. IBM Rational ClearQuest), a source version control system (e.g. IBM Rational ClearCase), or customer-specified databases with custom schema.

Data Persistence Tier

Data persistence is based on an RDBMS. PLS is designed using the Java JDO standard for object-relational mapping. In particular, it uses the KODO object relational persistence engine from Solarmetric, Inc. PLS uses the KODO Performance Pack, which provides caching and clustering for the maximum in scalability.

IDI supports PLS on most of the databases supported by Solarmetric, in particular the following.

• Oracle
• Informix
• DB2
• MySQL
• PostgreSQL
• SQLServer
• Sybase

Standards Compliance

Additional points of compliance with familiar IT standards and products:

• Client-side deployment via Java Web Start technology
• Role Based Access Control (ANSI / INCITS 359-2004)
• Java JDO standard for Object Relational Mapping
• Optional integration with LDAP for user authentication