Quick Start Guide

Set up the back-end database

First, let's set up a back-end database for our healthcare service. Follow the steps below to create the database.

1. Download the dataServiceSample.zip file from GitHub and extract it to a location on your computer.

   Let's refer to the extracted  dataServiceSample  directory as <QSG_HOME>, which contains the following:

   • A DB script to create the back-end database (DATA_SERV_QSG) with the channeling information of the healthcare service.
   • A pre-packaged data service (DOCTORS_DataService.dbs file), which can expose the back-end database as a service.

2. Open a terminal, navigate to the <QSG_HOME> directory, and execute the following command:

   ant -Ddshome=PATH_TO_EI_HOME

The  DATA_SERV_QSG  database is now created in the <EI_HOME>/samples/data-services/database directory with information of all available doctors in the healthcare service.

Expose the database as a data service

Now, let's start the ESB profile and upload the sample data service:

1. Start the ESB profile:

   If you have started the ESB profile previously, stop the server by pressing  Ctrl+C and restart it using the following commands.
2. In your Web browser, navigate to the WSO2 EI management console using the following URL: https://localhost:9443/carbon/
3. Log in to the Management Console using the following credentials:
   • Username: admin
   • Password: admin
4. Go to the Main tab and click Data Service > Upload. 
   
5. Upload the DOCTORS_DataService.dbs file from the <QSG_HOME> directory.
6. Refresh the page to see the deployed data service in the Deployed Services screen.

The database of the channeling service is now exposed through the DOCTORS_DataService data service, which we just deployed in WSO2 EI.

Request doctors' information

Assume that you want information on the availability of all surgeons. Open a terminal and execute the following command. Note that we are specifying 'surgery' as the specialty.

curl -v http://localhost:8280/services/DOCTORS_DataService/getDoctors?SPECIALITY=surgery

The information about the availability of all surgeons will be published on your terminal:

<DOCTORSLIST xmlns="http://ws.wso2.org/dataservice">
<DOCTOR>
    <NAME>thomas collins</NAME>
    <HOSPITAL>grand oak community hospital</HOSPITAL>
    <SPECIALITY>surgery</SPECIALITY>
    <AVAILABILITY>9.00 a.m - 11.00 a.m</AVAILABILITY>
    <CHARGE>7000</CHARGE>
</DOCTOR>
<DOCTOR>
    <NAME>anne clement</NAME>
    <HOSPITAL>clemency medical center</HOSPITAL>
    <SPECIALITY>surgery</SPECIALITY>
    <AVAILABILITY>8.00 a.m - 10.00 a.m</AVAILABILITY>
    <CHARGE>12000</CHARGE>
</DOCTOR>
<DOCTOR>
    <NAME>seth mears</NAME>
    <HOSPITAL>pine valley community hospital</HOSPITAL>
    <SPECIALITY>surgery</SPECIALITY>
    <AVAILABILITY>3.00 p.m - 5.00 p.m</AVAILABILITY>
    <CHARGE>8000</CHARGE>
</DOCTOR>
</DOCTORSLIST>

Congratulations, you have successfully sent a request to the data service!

Let's get started!

Configuring WSO2 EI

1. Open the <EI_HOME>/conf/jndi.properties file and add the following line after the queue.MyQueue = example.MyQueue line:

   queue.PaymentRequestJMSMessageStore=PaymentRequestJMSMessageStore

2. Start the Message broker profile:
3. Download the back-end service from GitHub. This will process appointment requests and copy it to the <EI_HOME>/wso2/msf4j/deployment/microservices directory. The back-end service is now deployed in the MSF4J profile, which will run microservices for your integration flows. 

4. Start the MSF4J profile to send requests to the back-end service:

   If you have started the MSF4J profile previously, skip this step.

   The Healthcare service is now active and you can start sending requests to the service.

5. Start the ESB profile:

   If you have started the ESB profile previously, skip this step.
6. Open the ESB profile Management Console using https://localhost:9443/carbon, and log in using admin as the username and the password.

7. Download the SampleServicesCompositeApplication_1.0.0.car file from GitHub.

   This file is a Carbon Application Archive (CAR file) containing the integration artifacts you will use in this tutorial, including:

   • An API resource, which acts as the endpoint that accepts incoming requests from a client, routes them to the back-end service for processing, receives a response from the service, and sends the response back to the client.
   • The back-end service that processes the appointment requests.
   • A Switch Mediator to route messages based on the message content to the relevant HTTP Endpoint defined in the ESB.
   • A Store Mediator to enqueues messages passing through its mediation sequence in a given message store.

8. Deploy the SampleServicesCompositeApplication_1.0.0.car file as follows:

   Note:  If you already deployed the SampleServicesCompositeApplication_1.0.0.car file when following the first part of the QSG, make sure to go to  Manage > Carbon Applications > List and delete it before proceeding to the below steps.

   1. On the Main tab of the management console, go to Manage > Carbon Applications and click Add. 

   2. Click Choose File, select the SampleServicesCompositeApplication_1.0.0.car file that you downloaded, and click Upload. 

   3. Refresh the page to see the carbon application you just added in the Carbon Applications List screen.
      

Sending requests to WSO2 EI

1. Create a JSON file named request.json with the following payload to specify the details the back-end service needs to make the appointment: patient information, doctor name, hospital name, and appointment date. 

   {
   "name": "John Doe",
   "dob": "1940-03-19",
   "ssn": "234-23-525",
   "address": "California",
   "phone": "8770586755",
   "email": "johndoe@gmail.com",
   "doctor": "thomas collins",
   "hospital": "grand oak community hospital",
   "cardNo": "7844481124110331"
   }

2. Open a command line terminal and execute the following command from the location where request.jsonfile you created is saved:

   curl -v -X POST --data @request.json http://localhost:8280/healthcare/categories/surgery/reserve --header "Content-Type:application/json"

   This command sends the JSON payload you created in the previous step to the API resource http://localhost:8280/healthcare/categories/surgery/reserve, which was included in the CAR file you uploaded. The API resource contains the logic for routing appointment requests to the back-end service you deployed in the microservices directory. 

   You will see the response as follows:

   {"message":"Payment request successfully submitted. Payment confirmation will be sent via email."}

3. Check the terminal window and you see that the response from SettlePaymentEP is logged as follows:

   [2018-06-07 11:46:48,936] [EI-Core]  INFO - LogMediator message = Routing to grand oak community hospital
   
   [2018-06-07 11:46:48,949] [EI-Core]  INFO - TimeoutHandler This engine will expire all callbacks after GLOBAL_TIMEOUT: 120 seconds, irrespective of the timeout action, after the specified or optional timeout
   
   [2018-06-07 11:46:52,003] [EI-Core]  INFO - LogMediator To: http://www.w3.org/2005/08/addressing/anonymous, WSAction: , SOAPAction: , MessageID: urn:uuid:995e37e3-8900-4da8-8eea-67da91de2c12, Direction: request, Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><jsonObject><appointmentNo>1</appointmentNo><doctorName>thomas collins</doctorName><patient>John Doe</patient><actualFee>7000.0</actualFee><discount>20</discount><discounted>5600.0</discounted><paymentID>eb83d9cc-0230-4dc8-a613-33b419cebbd7</paymentID><status>Settled</status></jsonObject></soapenv:Body></soapenv:Envelope>

Congratulations, you have successfully sent a message to the WSO2 ESB profile!