Developing InfrastructureBased eServices

1
Developing Infrastructure-Based e-Services

• Adegboyega Ojo, Gabriel Oteniya
• UNU-IIST

2
Building an e-Service

• The following five steps are involved in
  developing a complete e-service
• define the Business Process underlying the
  service and deploy the formal process definition
  in the Internal Workflow Engine (WFE)
• build the FO Application
• build the BO Application
• integrate the FO and BO Applications with the
  Mid-Office (WFE)
• integrate the BO Application with xG2G

3
Step 1 Define and Deploy BP

• How to define and deploy a new business process
• provide a model of the business process
  underlying associated service, typically using an
  Activity Diagram
• encode the business process in a specific process
  language supported by the Internal Workflow
  Engine, for instance JPDL supported by JBoss
• deploy the encoded process in the Internal
  Workflow Engine

4
Step 2 Build FO Application

• How to build an FO Application from the FO
  Framework
• design the interfaces for users, e.g. submitting
  application forms and tracking requests
• design the interfaces for agency officers, e.g.
  for checking the completeness of supporting
  documents
• use the Front Office Framework as a library to
  develop the FO
• design the relevant table schemas for persistence

5
Step 3 - Build BO Application

• How to build a BO Application from the BO
  Framework
• design the work-list for receiving requests
  arriving from FO via MO
• for each interactive step of the BP provide the
  necessary task forms
• using the BO Framework add functionalities to the
  task forms
• design relevant table schemas for persistence

6
Step 4- Integrate FO, BO and MO

• How to integrate FO and MO
• configure MOs Queue for receiving requests from
  Front Office
• use the FO Framework to publish FO requests into
  the queue
• How to integrate BO with MO
• retrieve tasks generated by the Internal Workflow
  Engine from MOs Outgoing Queue through the BO
  Framework
• insert the end-of -task signals into the MOs
  Incoming Queue using the BO Framework

7
Step 5 Integrate BO and xG2G

• How to use the xG2G API
• register a BO Application as a member of the
  gateway
• create channels for communicating with other
  applications
• inform partner applications to register and
  subscribe to channels
• enable and configure available extensions as
  desired

8
The e-Licensing Example

• The e-Licensing application was developed based
  on these 5 steps
• The e-Licensing System consists of
• A Front Office Application
• A Back Office Application
• A Mid Office Application (or Internal Workflow
  Engine)
• The Internal Workflow was developed during
  e-service development (Tasks 3 and 4) and
  presented at the 3rd Workshop in July 2005.

9
Providing One-Stop-Services

• The following steps are required to deliver a
  one-stop-service through the
• Government-Wide Workflow Engine
• define the high-level business process and encode
  it in BPEL
• (Business Process execution Language)
• deploy the BPEL process in an Orchestration
  Server, e.g. ActiveBPEL, Oracle Business Process
  Manager or BizTalk.
• develop a Service Agent using GovWFs API for
  invoking the BP
• deploy Service Agent using GovWF Admin to obtain
  a Service ID
• associate the Service ID with a request on the
  one-stop portal

10
Conclusion

• The five basic steps for building an e-service
  using infrastructure elements were presented.
• Experience shows that while FO Applications can
  be developed rapidly, the complexity of BO
  Application is process-dependent.
• The available MO is highly reusable evidence of
  the direct use without any modification of the
  demo development.
• Using xG2G is simple - registering as member,
  creating channels and sending messages to channel
  subscribers.
• The usage of GovWF is also straightforward once
  the BPEL process is available and the Service
  Agent is developed.