HP ServiceCenter from a developer perspective

Tags: HP ServiceCenter, RAD, HP Service Manager, JavaScript

· Basically the architecture of HP ServiceCenter with regards to tailoring seems to be something like this:


RTE/JRTE – (Java) Runtime Environment?

I’m not sure of the name, although Runtime Environment fits nicely with what it does.

This is the core functionality delivered, and implements basic features like data access, rtecalls (think of them as system calls), etc. In other words: the binaries shipped with the product.

RAD – Rapid Application Development?

Not sure about the name here either.

They are described as a panel based language in the manual. To me it helps thinking about them as a flowchart, with each panel being a component of the flowchart.

Each panel has two or more exits; of one is always the error exit.

RADs are at the core of the product as they are executed immediately a session is established; the first RAD is the logon RAD.

So basically, whenever something happens in ServiceCenter, at least one RAD is on the stack. Usually at least two, since the first RAD executed is the Logon RAD, followed by the RAD configured on the operator record or the ESS rad.


These are basic expressions like assignments, logical or rte-calls (think of them as system calls) that are executed whenever a particular object is executed.

Mostly it’s RADs that are configured to execute them.

Some examples of objects with expressions are Format Controls which sits between the form and data, Display Options which are kind of menu items, etc.

The execution of expressions on various objects are handled akin to the JavaScript eval() function.


Added later, built on top of the RTE, although executed from RADs.

No Comments

Add a Comment