Before you begin,
- Download the product installer from here, and run the installer.
Let's call the installation location of your product the
Note that if you used the product installer to install your product, the
<EI_HOME>is located in a place specific to your OS as shown below:
OS Home directory Mac OS
- Select and download the relevant EI tooling ZIP file based on your operating system from here and then extract the ZIP file.
The path to this folder will be referred to as
<EI_TOOLING>throughout this tutorial.
- If you did not try the Storing and Forwarding Messages tutorial yet, open the WSO2 EI Tooling environment, click File, and then click Import. Next, select Existing WSO2 Projects into workspace under the WSO2 category, click Next and upload the pre-packaged project. This contains the configurations of the Storing and Forwarding Messages tutorial so that you do not have to repeat those steps.
- Download the MSF4J service from here and copy the JAR file to
<EI_HOME>/wso2/msf4j/deployment/microservicesfolder. The back-end service is now deployed in the MSF4J profile of WSO2 EI.
Let's get started!
Setting up the message broker profile
<EI_HOME>/conf/jndi and add the following line after the
queue.MyQueue = example.MyQueue line:
Creating the credentials for using the Gmail Connector
Creating a Client ID and Client Secret
Follow the steps below if you want to use your own email address for sending the emails.
- As the email sender, navigate to the URL https://console.developers.google.com/projectselector/apis/credentials and log in to your google account.
If you do not already have a project, create a new project.
Click Google APIs -> Credentials -> Create Credential -> OAuth client ID.
At this point, if the consent screen name is not provided, you will be prompted to do so.
Select Web Application and create a client.
Provide https://developers.google.com/oauthplayground as the redirect URL under Authorized redirect URIs and click Create.
The client ID and client secret will then be displayed.
See Gmail API documentation for details on creating the Client ID and Client Secret.
Click on the Library on the side menu, and select Gmail API.
Obtaining the Access Token and Refresh Token
Follow these steps to automatically refresh the expired token when connecting to Google API:
- Navigate to the https://developers.google.com/oauthplayground URL, click at the top right corner of the screen, and select Use your own OAuth credentials.
- Provide the client ID and client secret you previously created and click Close.
- Now under Step 1, select Gmail API v1 from the list of APIs, select all the scopes listed under it, and click Authorize APIs.
- You will then be prompted to allow permission, click Allow.
- Under Step 2, click Exchange authorization code for tokens to generate an display the access token and refresh token.
Importing the Gmail Connector into EI-Tooling
- Right click on Sample Services in the Project Explorer and Select Add or Remove Connector.
- Select Add Connector and click Next.
- Select Connector Store location and click Connect to connect to WSO2 Connector store.
- Scroll down and select Gmail from the list of connectors.
- Click Finish.
The connector is now downloaded into your Tooling environment and the connector operations will be available in the Gmail Connector palette.
Let's use these connector operations in the configuration.
Creating the Deployable Artifacts
The connector operations are used in the PaymentRequestProcessingSequence. Select this sequence, and do the following updates:
Add a Property Mediator just before the Call mediator to retrieve and store the patient's email address.
With the Property mediator selected, access the Property tab of the mediator and fill in the information in the following table:
Field Value Property Name Select New Property New Property Name email_id Property Action Select Set Value Type Select Expression Value Expression json-eval($.patient.email) Description Get Email ID
Add another Property mediator just after the Log mediator to retrieve and store the response sent from SettlePaymentEP. This will be used within the body of the email.
With the Property mediator selected, access the Property tab and fill in the information in the following table:
Field Value Property Name Select New Property New Property Name payment_response Property Action Select Set Value Type Select Expression Value Expression json-eval($.) Description Get Payment Response
Drag and drop the init method from the Gmail Connector palette adjoining the Property mediator you added in the previous step.
With the init method selected, access the Property tab and fill in the information in the following table:
Field Value Parameter Editor Type Select inline userId The sender's email address (use the email address that you used to configure the client ID and secret.) accessToken The access token you obtained. apiUrl https://www.googleapis.com/gmail clientId The client ID you created. clientSecret The client secret you created. refreshToken The refresh token you obtained.
Add the sendMail method from the Gmail Connector palette and access the Property tab and fill in the information in the following table:
Field Value Description Parameter Editor Type Select inline to
Retrieves the patient email address that was stored in the relevant Property mediator. subject Payment Status The subject line in the email that is sent out. messageBody
Retrieves the payment response that was stored in the relevant Property mediator.
The updated PaymentRequestProcessingSequence should now look like this:
- Save the updated sequence configuration.
- Right click on SampleServicesConnectorExporter and navigate to New -> Add/Remove Connectors and select Add connector and click on Next. Select Workspace to list down the connectors that were added.
Select the Gmail connector from the list and click OK and then Finish.
Packaging the artifacts
Since you added a connector to the Connector Exporter Project, this will need to be packaged into our existing C-App.
Package the C-App names SampleServicesCompositeApplication project with the artifacts created.
Ensure the following artifact check boxes are selected in the Composite Application Project POM Editor.
Starting the Message Broker runtime
Start the message broker profile as follows:
The message broker profile is now ready to receive messages from the ESB profile.
Starting the MSF4J profile
To be able to send requests to the back-end service (which is an MSF4J service deployed in MSF4J profile), you need to first start the MSF4J runtime:
The Healthcare service is now active and you can start sending requests to the service.
Starting the ESB runtime and deploying the artifacts
On the Servers tab, expand the WSO2 Carbon server, right-click SampleServicesCompositeApplication, and choose Redeploy. The Console window will indicate that the CApp has been deployed successfully.
If you do not have a server added in Eclipse, refer this tutorial.
You can also deploy the artifacts to the ESB profile of WSO2 EI using a Composite Application Archive (CAR) file.
Sending requests to the ESB
Create a JSON file names
request.jsonwith the following request payload. Make sure you provide a valid email address so that you can test the email being sent to the patient.
Open a command line terminal and execute the following command from the location where
request.jsonfile you created is saved:
This is derived from the URI-Template defined when creating the API resource.
You will see the response as follows:
An email will be sent to the provided patient email address with the following details:
You have now explored how to import the Gmail connector to the ESB profile of WSO2 EI and then use the connector operation to send emails.