Tag Archives: integration

Mulesoft : Create Cloudhub Notification

28 Tuesday Apr 2020

Posted by in Integration, MuleSoft, SOA

≈ Leave a comment

Tags

, , , , ,

We need different types of nontifications when creating an integration application using Mule or any other technology. We can of course use something like email or SMTP or any other specific API, but that ties the code strongly to the implementation. A better option is to use Mule Cloudhub’s Notifications which can generate different types of alerts with lot of details and also send email if required.

There are of course 2 parts to the solution –

A) Configuration and Setup in CloudHub

Follow instructions here to setup alert in CloudHub. These instructions work well, so I won’t repeat those.

B) Configuration and coding in Anypoint Studio

      1. Add Cloudhub Connector to your application. If you do not find it, download it from exchange inside your studio.
        1
      2. In your error handler flow, add a Cloudhub Create Notification component.
        2
      3. You may need to define a Cloudhub Configuration, Use your cloudhub username, password and environment details to do this.
      4. Now in the code open the file in XML, you can do this using the visual UI as well, but I prefer this in XML.
      5. Create a subflow to handle actual notifications
        3
        You can add any number of custom properties and then refer to them when creating your notification in CloudHub
      6. Call the subflow from your error handler section
        4

     

Siebel CRM On Demand Web Services – Contact Search using SoapUI

11 Monday Apr 2011

Posted by in Camel, Integration, Java, Siebel, SOA

≈ 10 Comments

Tags

, , , ,

Before we begin using Siebel CRM On Demand’s web services, we require the WSDL files. The WSDL files are specific to the account and can be downloaded by logging in to Siebel COD.

Create a new SoapUI project and add the WSDL as initial WSDL. SoapUI will create a new project with placeholder requests for all operations. Let’s open ContactQueryPage operation from SoapUI.

The endpoint path will be something like – https://secure-ausoxxxxx.crmondemand.com/Services/Integration
This path is  unique to your instance of Siebel COD.

Next lets remove the body of input and replace it with –

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header/>
<soapenv:Body>
     <con:ContactQueryPage_Input xmlns:con="urn:crmondemand/ws/ecbs/contact/" xmlns:quer="urn:/crmondemand/xml/Contact/Query">
        <quer:ListOfContact startrownum="0" pagesize="100" recordcountneeded="true">
            <quer:Contact searchspec="[ContactFirstName] LIKE 'John'">
                <quer:Id/>
                <quer:ContactFirstName/>
                <quer:ContactLastName/>
                <quer:AccountId/>
            </quer:Contact>
        </quer:ListOfContact>
    </con:ContactQueryPage_Input>
</soapenv:Body>
</soapenv:Envelope>

This results in Soap Fault response with Siebel error code SBL-ODU-01006 and message : “Internal Error: Session is not available. Aborting.”
This is because we still haven’t added username/password for authentication. There is another option to first get the session and then pass that value in header of the request. However I prefer to use the Stateless version above, as it separates the responsibility of handling session.

Let’s make 2 changes to fix this error.
1) Replace first line of the SOAP request with –

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/07/secext">

2) Add these lines just below the SOAP Envelope element –

<soapenv:Header>
   <wsse:Security>
      <wsse:UsernameToken>
         <wsse:Username>your_siebel_username</wsse:Username>
         <wsse:Password Type="wsse:PasswordText">your_siebel_password</wsse:Password>
      </wsse:UsernameToken>
   </wsse:Security>
</soapenv:Header>

What we’ve done here is added WS-SECURITY headers to the SOAP request.
Now the request should run just fine.

Note –
1) You need to add any fields you need to the request before they can be returned by Siebel CRM. e.g., <ContactFirstName/>
2) Its better to confirm data actually exists by logging through web-console.