Get Started with STAR Integrations

STAR Integration apps for Automotive Cloud uses a WSDL-based implementation to service requests from external systems. Customers can download the resource BOD zip file, unzip it, and import the WSDL file to the SoapUI editor to make edits and then run the application.

Prerequisites

We recommend using the SoapUI web application, as it defines the structure of the request body automatically. If you use another web application, you have to prepare a payload manually to call an API. Sample requests aren’t available with other web applications.

Learn about the different types of STAR Integration apps in Automotive Cloud and when to use them. See Overview of STAR Integrations.

Create a connected app to set up the client credentials flow. See Configure a Connected App for the OAuth 2.0 Client Credentials Flow for details.

Deploy the automotive cloud applications from MuleSoft Direct to your MuleSoft instance.

  1. Download the Business Object Document (BOD) zip folder. A BOD is a combination of the Application Area, Data Area, Verb, and Noun.
    Resource NameWSDL File
    Customer InformationCustomerInformation.zip
    Repair OrderRepairOrder.zip
    Sales LeadSalesLead.zip
    Vehicle InventoryVehicleInventory.zip
    Vehicle SpecificationsVehicleSpecification.zip
  2. Unzip the downloaded BOD file to get the WSDL file and the dependent application. The folder also contains other BOD files and resource files that are required for WSDL import. For example, when you unzip the Customer Information.zip, you get CustomerInformation.wsdl, which you must import into SoapUI. The other artifacts that Customer Information.zip contains are BODs, Resources, and STARWSDLDataTypes4.xsd.
  1. In SoapUI, click SOAP.
  2. In the New SOAP Project dialog, specify a project name.
  3. Browse your local folder to add the path to the WSDL file or service in the Initial WSDL field.
  4. Leave the default settings and click OK.

SoapUI loads the specified WSDL and parses its contents to show the service operations in the navigator tree.

  1. Add the authorization headers.
    1. In the SoapUI editor, click the Auth tab.
    2. From the Authorization dropdown, select Add New Authorization and then select Basic.
    3. Click OK.
  2. Configure authorization.
    1. Specify the username and password that must be used for the standard basic authorization. The username is the Client ID, and the password is the Client Secret created as part of the prerequisites.

Modify the request XML payload and send the request. In SoapUI editor, the service operations are shown as nodes under the WSDL Service node in the project navigator. By default, SoapUI also creates a sample request (Request 1) for each operation when importing WSDL.

  1. Double-click to open the service request for an operation and edit the parameters per the requirements. For field-mapping details, see Resource Mappings.
  2. Edit request URL. Replace the URL placeholder with the host or domain of the MuleSoft application. You can also copy the URL directly from the MuleSoft Direct user interface. Automotive Cloud Integrations API uses the following format: <Domain name>/star/<Resource type.
  3. Run the application.
  4. Run the application.