TappS™ service creation is based on Java component technology. Services are created using the TappS Service Creation Environment, delivered to an active TappS NSC, and installed using the TappS Element Management System. The system utilizes dynamic mapping and loading of Java classes to allow a service to be updated without downtime, allowing service sessions in progress to complete using the pre-update software while new sessions start using the updated service.

Service creation is done either by the TappS Service Creation Environment, which uses a graphical environment allowing user to assemble services from pre-defined components, or by using a standard Java development environment such as Eclipse and interface information describing the Java APIs to build new Java components which define a service. Both methods produce a standard Java Archive (JAR) file and an XML definition of the parameter data in the service. These are used by the TappS management system to control installation and activation of the service.

Services are built on a set of Java APIs, which include both standard JAIN APIs (JAIN Call Control, Parlay UI, JAIN Simple, etc.), APIs to the SLEE itself for receiving and generating events, and APIs presented by “building block” components, which perform common service functions, such as conducting an IVR dialog with a user, computing charges, or directing a call according to a set of rules. These building block functions reduce the work of the service developer by making service creation and customization easier, but unlike traditional building block environments the developer isn’t limited to using only the building blocks provided but free to develop any function needed using standard Java APIs.