JSDN Connector Development

• The sample Service depicted below is a multi‐tenant, web‐enabled, SaaS application.
• The chargeback method employed by this application is an automated post‐consumption method where a department is automatically charged periodically.

  Services Lifecycle

  1. Customer registers and places an order for, say, 25 licenses of the Service (e.g. a desktop backup application from a SaaS application provider)
  2. Customer organization is created and provisioned to 25 units.
  3. Customer is provided access to the application.
  4. Customer organization creates users and allocates the units they have ordered.
  5. User of the customer organization are provisioned and provided access to the application.
  6. Users start consuming the application.
  7. A chargeback is generated at the end of every billing cycle.
  8. During the course of consuming the application
  • Steps 4, 5, 6, 7 are repeated in a cyclic manner.
  • Customer can choose to increase/decrease the number of licenses.
  • CRUD/MAC operations are performed.

• Is a program or a component, which integrates a third party application with the Jamcracker
• Platform for the purpose of Service provisioning.
• Can communicate organizations and users profiles in the Jamcracker Platform to the application or Service.
• Can be developed by a Certified Jamcracker Connector Developer who can be a SI (Systems Integrator), an ISV (Independent Software Vendor) or an ASP (Application Service Provider).
• Can be integrated into Jamcracker Platform on the fly.
• Manages organization/user identity in the application or Service
• Enables a zero touch, automated process to provision an organization and user to an application.

1. This mechanism of integration does not require any knowledge of the Jamcracker Platform and Connector s (Integrations) can be written and tested independently. This is a platform independent approach to integration where a Connector can be developed using the Application’s native language or technology.
2. The Jamcracker Platform provides all the data required to create an organization or user in the third party application in XML format for integration purposes. This process of creating the entities in the third party application is called Provisioning.
3. The third party application provider has to expose a Web interface that can accept the XML. The Jamcracker Platform will post the XML request to this Web interface exposed. The Jamcracker Platform will post this request only over a secure layer, using HTTP over SSL (i.e., HTTPS).
4. The Web interface needs to accept the request from the Jamcracker Platform, needs to read the XML from
5. POST parameter name “request”, parse the data, and extract required data using a parsing mechanism.
6. The parsed data is used to create organization or user entities in the third party application.
7. The application will provide a response back to Jamcracker via a pre‐defined XML format. This response will notify the Jamcracker Platform of the success/failure of the operation and optionally send more information that needs to be populated back in the Jamcracker Platform.
8. The Jamcracker Platform will accept the XML and fetch the status of provisioning.

<!ELEMENT authinfo ( username, password ) >
<!ELEMENT body ( request ) >
<!ELEMENT command ( entitydata+ ) >
<!ATTLIST command name ( create | update | delete | sso ) #REQUIRED > <!ATTLIST command type ( company | user ) #REQUIRED > <!ELEMENT datafield ( name, value ) >
<!ATTLIST datafield datatype ( URL | int | string | date) #REQUIRED > <!ELEMENT entitydata ( datafield* ) >
<!ATTLIST entitydata entitytype ( service | company | user ) #REQUIRED
>
<!ELEMENT header ( authinfo ) >
<!ELEMENT jcprovisionmessage ( header, body ) > <!ELEMENT name ( #PCDATA ) > <!ELEMENT password ( #PCDATA ) >
<!ELEMENT request ( command ) >
<!ELEMENT username ( #PCDATA ) >
<!ELEMENT value ( #PCDATA ) >

<?xml version="1.0" encoding="UTF-8" ?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:element name="authinfo"> <xs:complexType>
<xs:sequence>
<xs:element ref="username" />
<xs:element ref="password" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="body">
<xs:complexType>
<xs:sequence>
<xs:element ref="request" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="command">
<xs:complexType>
<xs:sequence>
<xs:element ref="entitydata" minOccurs="2" maxOccurs="3" /> </xs:sequence>
<xs:attribute name="name" type="commandName" use="required" />
<xs:attribute name="type" type="commandType" use="required" />
</xs:complexType>
</xs:element>
<xs:simpleType name="commandType">
<xs:restriction base="xs:string">
<xs:enumeration value="user"/>
<xs:enumeration value="company"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="commandName">
<xs:restriction base="xs:string">
<xs:enumeration value="create"/>
<xs:enumeration value="update"/>
<xs:enumeration value="delete"/>
<xs:enumeration value="sso"/>
</xs:restriction>
</xs:simpleType>
<xs:element name="datafield">
<xs:complexType>
<xs:sequence>
<xs:element ref="name" />
<xs:element ref="value" />
</xs:sequence>
<xs:attribute name="datatype" use="required"> <xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="URL" />
<xs:enumeration value="int" />
<xs:enumeration value="string" />
<xs:enumeration value="date" />
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
</xs:element>
<xs:element name="entitydata">
<xs:complexType>
<xs:sequence>
<xs:element ref="datafield" minOccurs="0" maxOccurs="unbounded" /> </xs:sequence>
<xs:attribute name="entitytype" type="entitytypevalues"
use="required"/>
</xs:complexType>
</xs:element>
<xs:simpleType name="entitytypevalues">
<xs:restriction base="xs:string">
<xs:enumeration value="service"/>
<xs:enumeration value="company"/>
<xs:enumeration value="user"/>
</xs:restriction>
</xs:simpleType>
<xs:element name="header">
<xs:complexType>
<xs:sequence>
<xs:element ref="authinfo" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="jcprovisionmessage">
<xs:complexType>
<xs:sequence>
<xs:element ref="header" />
<xs:element ref="body" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="name">
<xs:complexType mixed="true" />
</xs:element>
<xs:element name="password" type="xs:string" />
<xs:element name="request">
<xs:complexType>
<xs:sequence>
<xs:element ref="command" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="username" type="xs:string" /> <xs:element name="value"> <xs:complexType mixed="true" />
</xs:element>
</xs:schema>

<!ELEMENT body ( response ) >
<!ELEMENT command ( entityresponse, entitydata* ) >
<!ATTLIST command name ( create | update | delete | sso ) #REQUIRED > <!ATTLIST command type ( company | user ) #REQUIRED > <!ELEMENT datafield ( name, value ) >
<!ATTLIST datafield datatype ( URL | int | string | date) #REQUIRED > <!ELEMENT entitydata ( datafield* ) >
<!ATTLIST entitydata entitytype ( company | user | sso ) #REQUIRED > <!ELEMENT entityresponse ( faultcode, faultstring ) >
<!ELEMENT faultcode ( #PCDATA ) > <!ELEMENT faultstring ( #PCDATA ) > <!ELEMENT jcprovisionmessage ( body ) > <!ELEMENT name ( #PCDATA ) > <!ELEMENT response ( command ) > <!ELEMENT value ( #PCDATA ) >

<?xml version="1.0" encoding="UTF-8" ?>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="body">
<xs:complexType>
<xs:sequence>
<xs:element ref="response" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="command">
<xs:complexType>
<xs:sequence>
<xs:element ref="entityresponse" />
<xs:element ref="entitydata" maxOccurs="unbounded"
minOccurs="0"/>
</xs:sequence>
<xs:attribute name="name" type="eventName" use="required" />
<xs:attribute name="type" type="allowedEntityTypes"
use="required" />
</xs:complexType>
</xs:element>
<xs:element name="datafield">
<xs:complexType>
<xs:sequence>
<xs:element ref="name" />
<xs:element ref="value" />
</xs:sequence>
<xs:attribute name="datatype" type="xs:NMTOKEN" use="required"/>
</xs:complexType>
</xs:element>
<xs:element name="entitydata">
<xs:complexType>
<xs:sequence>
<xs:element ref="datafield" maxOccurs="unbounded"/> </xs:sequence>
<xs:attribute name="entitytype" type="allowedEntityTypes"
use="required" />
</xs:complexType>
</xs:element>
<xs:element name="entityresponse">
<xs:complexType>
<xs:sequence>
<xs:element ref="faultcode" />
<xs:element ref="faultstring" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="faultcode">
<xs:complexType mixed="true" />
</xs:element>
<xs:element name="faultstring">
<xs:complexType mixed="true" />
</xs:element>
<xs:element name="jcprovisionmessage">
<xs:complexType>
<xs:sequence>
<xs:element ref="body" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="name">
<xs:complexType mixed="true" />
</xs:element>
<xs:element name="response">
<xs:complexType>
<xs:sequence>
<xs:element ref="command" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="value">
<xs:complexType mixed="true" />
</xs:element>
<xs:simpleType name="allowedEntityTypes"> <xs:restriction base="xs:string"> <xs:enumeration value="company"/> <xs:enumeration value="user"/> <xs:enumeration value="sso"/> </xs:restriction>
</xs:simpleType>
<xs:simpleType name="eventName">
<xs:restriction base="xs:string">
<xs:enumeration value="create"/>
<xs:enumeration value="update"/>
<xs:enumeration value="delete"/>
<xs:enumeration value="sso"/>
</xs:restriction>
</xs:simpleType>
</xs:schema>