See also: StarConnect Data Server Parameters
The StarConnect Data Server (STCDS) is a general purpose vehicle for bidirectional, asynchronous data exchange of central Daimler marketing, sales, aftersales systems. The data server will act as the communication server for synchronous and asynchronous data exchange between Autoline and external systems. Related topics are:
The STCDS can offer an interface per retailer. Each retailer is identified via an external system ID, equal to the Global Standard Source for Networkdata (GSSN) dealer number of the main outlet of the dealer. Additional locations (site/outlet) of that retailer will use the same credentials for communicating with the STCDS.
Note: The setup within Autoline for STCDS is based on the external system ID (GSSN ID) of the retailer and not the Autoline company (site/outlet) structure.
STCDS quick overview:
STCDS data transfer:
Asynchronous interface: Asynchronous (offline) communication requests is used when batch update rather than
real-time information is required.
Autoline will request data available on STCDS either on request or as part of Timed operations. The communication protocol SOAP over HTTPS is used for this communication. The underlying communication protocol is HTTPS and thus synchronous. The name of this use case, offline or asynchronous, stems from the business communication which is not latency critical because it is not in loop with an end-user GUI. The asynchronous interface is also used for synchronous requests initiated by Autoline.
Synchronous interface (initiated by Autoline): Synchronous communication is used in case a backend system (for example, MBC POS) requires
real-time information from Autoline.
All communication between the backend system and Autoline is realized via the StarConnect Data Server (STCDS). The online communication is established over a persistent HTTPS channel. This HTTPS channel is initiated by Autoline to STCDS which resides on the internet. This persistent channel remains open during the day and is only closed when the Autoline server becomes unavailable when processing the end-of-day function of Timed operations.
The Communication Module form maintains and handles all asynchronous communication between Autoline and the STCDS for the selected external system ID.
This form is displayed when you click Manufacturer-specific > MB. Mercedes-Benz > Menu - Utilities > StarConnect Data Server > StarConnect data server. It maintains and handles all asynchronous communication between Autoline and the STCDS for the selected external system ID.
Menu Bar and Toolbar:
| Menu bar | Toolbar | Action |
|---|---|---|
| File > New |  |
Creates a communication type record ready for you to complete. Note: This option is only available when the Communication types tab is selected and the Autoline user has a priority level of 7 or higher. Tip: Please consider to use the Add Default Communication Types function to create all relevant communication types automatically instead of adding all required communication types manually. |
| File > Edit |  |
Maintains the selected communication record on the tab required. |
| File > Delete |  |
Deletes an existing communication record.
Note: This option is only available when the Inbound queue, Outbound queue or Synchronous request tab is selected for unprocessed data records and the Autoline user has a priority level of 7 or higher. |
| File > Exit |  |
Returns you to the previous menu. |
| Edit > Copy |  |
Creates a communication type record populated with data from the gridline which you selected on the Communication types tab. Note: This option is only available when the Communication types tab is selected and the Autoline user has a priority level of 7 or higher. |
| Tools > Start daemon |  |
Starts the communication daemon which handles all the asynchronous communication with STCDS. |
| Tools > Stop daemon |  |
Stops the communication daemon which handles all the asynchronous communication with STCDS. Note: This option is only available for Autoline users with a priority level of 8 or higher. |
| Tools > Processing modules | — | Displays details of the available processing modules for the selected external system ID, including the synchronous communication operations in case the processing module is active on the persistent line. |
| Tools > Default communication types | — | Creates the required communication types per processing module, if the installed and set up, for the selected external system ID. Note: This option is only available when the Communication types tab is selected and the Autoline user has a priority level of 7 or higher. |
| View > Refresh |  |
Populates the information displayed in the grid of the selected tab in case of new or changed data records. |
| Help > Help |  |
Displays this help topic in a web browser. |
| Help > About | — | Displays version and copyright information. |
Field:
External system ID: Select to populate all available information on the Communication Module form related to the External system ID. The External system ID is setup in the StarConnect Data Server Parameters and displays the GSSN dealer number of the main outlet of the dealer (retailer). The external system ID's are available based on the mapping of the StarConnect Data Server Parameters - [External System ID <-> Company Mapping] form and the Autoline user's access level for the concerning module/company.
Tabs:
Displays all inbound queue details which are received from the STCDS. After entering the filter details, the grid is refreshed with the inbound queue details that meets the filter.
Filters on Inbound Queue tab:
Type: Select to filter the inbound queue details on the required communication type. The list contains all available communication types with the inbound communication direction for the selected External ID.
Event date: Enter the start and end date to filter the inbound queue details on the event date. The event date and time are provided by the STCDS and are the actual date- and timestamps when the data was sent to the data server by the source system (date that the data record became effective from a business point of view).
Search text: Enter a word / number or part of the word / number to filter the inbound queue details on the Business ID, Data ID, Result code, Processing module and File name. You can use wildcards in the filter, for example * and ?.
Status [option buttons]:
- Unprocessed: Select to filter the inbound queue details on unprocessed records, the New and Error fields are available for additional filtering. The Processed option button is cleared and the Processed and Archived fields appear shaded.
- Processed: Select to filter the inbound queue details on processed records, the Processed and Archived fields are available for additional filtering. The Unprocessed option button is cleared and the New and Error fields appear shaded.
New: Select to display inbound queue details for all new unprocessed records. Available if the Unprocessed option button is selected.
Error: Select to display inbound queue details for all unprocessed records with an error detected. Available if the Unprocessed option button is selected.
Processed: Select to display inbound queue details for all processed records that are not in archive. Available if the Processed option button is selected.
Archived: Select to display inbound queue details for all processed records that are archived. Available if the Processed option button is selected.
Grid on Inbound Queue tab:
Status: Displays the status of the inbound data record:
New: Received inbound data record, not processed (yet).
Error: Received inbound data record, not processed. An error is detected, possible causes:
- Validation error of the data against the corresponding XSD
- Error is set by the corresponding processing module
Processed: Received inbound data record that is processed, not archived (yet).
Archived: Received inbound data record that is processed and archived.
Type: Displays the communication type.
Description: Displays the description of the use for the communication type.
Business ID: Displays the unique Business ID as specified by the interface.
Version: Displays the business version of the data record.
Event date: Displays the date that the data record became effective from a business point of view. The event date and time are provided by the STCDS and are the actual date- and timestamps when the data was sent to the data server by the source system.
Result code: Displays the result code which is provided by the STCDS when the data is downloaded from the data server.
Tip: The ToolTip of this cell will display the result code including the description, if available.
Grid Shortcut Menu on Inbound Queue tab:
Open: Maintains the selected inbound data record.
Displays all outbound queue details which are sent to the STCDS. After entering the filter details, the grid is refreshed with the outbound queue details that meets the filter.
Filters on Outbound Queue tab:
Type: Select to filter the outbound queue details on the required communication type. The list contains all available communication types with the outbound communication direction for the selected External ID.
Event date: Enter the start and end date to filter the outbound queue details on the event date. The event date and time are the actual date- and timestamps when the data record is created in the outbound queue.
Search text: Enter a word / number or part of the word / number to filter the outbound queue details on the Business ID, Data ID, Result code, Processing module and File name. You can use wildcards in the filter, for example * and ?.
Status [option buttons]:
- Unprocessed: Select to filter the outbound queue details on unprocessed records, the New and Error fields are available for additional filtering. The Processed option button is cleared and the Processed and Archived fields appear shaded.
- Processed: Select to filter the outbound queue details on processed records, the Processed and Archived fields are available for additional filtering. The Unprocessed option button is cleared and the New and Error fields appear shaded.
New: Select to display outbound queue details for all new unprocessed records. Available if the Unprocessed option button is selected.
Error: Select to display outbound queue details for all unprocessed records with an error detected. Available if the Unprocessed option button is selected.
Processed: Select to display outbound queue details for all processed records that are not in archive. Available if the Processed option button is selected.
Archived: Select to display outbound queue details for all processed records that are archived. Available if the Processed option button is selected.
Grid on Outbound Queue tab:
Status: Displays the status of the outbound data record:
New: Created by Autoline outbound data record, not processed (yet).
Error: Created by Autoline outbound data record, not processed. An error is detected, possible causes:
- Validation error of the data against the corresponding XSD
- Error is set by the corresponding processing module
Processed: Created by Autoline outbound data record that is processed, not archived (yet).
Archived: Created by Autoline outbound data record that is processed and archived.
Type: Displays the communication type.
Description: Displays the description of the use for the communication type.
Business ID: Displays the unique Business ID as specified by the program that created the outbound queue record.
Version: Displays the business version of the data record.
Event date: Displays the date that the data record became effective from a business point of view. The event date and time are the actual date- and timestamps when the data record is created in the outbound queue.
Result code: Displays the result code which is provided by the STCDS when the data is uploaded to the data server.
Tip: The ToolTip of this cell will display the result code including the description, if available.
Grid Shortcut Menu on Outbound Queue tab:
Open: Maintains the selected outbound data record.
Displays all synchronous requests details, initiated by Autoline. With a synchronous request an answer is directly received from the backend system. After entering the filter details, the grid is refreshed with the synchronous requests details that meets the filter.
Filters on Synchronous Requests tab:
Type: Select to filter the synchronous requests details on the required communication type. The list contains all available communication types with the synchronous communication direction for the selected External ID.
Event date: Enter the start and end date to filter the synchronous requests details on the event date. The event date and time are the actual date- and timestamps when the data record is created as a synchronous request (date that the data record became effective from a business point of view).
Search text: Enter a word / number or part of the word / number to filter the synchronous requests details on the Business ID, Data ID, Result code, Processing module and File name. You can use wildcards in the filter, for example * and ?.
Status [option buttons]:
- Unprocessed: Select to filter the synchronous requests details on unprocessed records, the Processed option button is cleared. Standard all records are processed as this is normally initiated by Autoline, unless an error occurred.
- Processed: Select to filter the synchronous requests details on processed records, the Unprocessed option button is cleared.
Grid on Synchronous Requests tab:
Status: Displays the status of the synchronous data record:
New: Created by Autoline synchronous data record, not processed (yet).
Error: Created by Autoline synchronous data record, not processed. An error is detected, possible causes:
- Validation error of the data against the corresponding XSD
- Error is set by the corresponding processing module
Processed: Created by Autoline synchronous data record that is processed, not archived (yet).
Archived: Created by Autoline synchronous data record that is processed and archived.
Type: Displays the communication type.
Operation: Displays the name of the operation which is triggered.
Business ID: Displays the unique Business ID as specified by the program that created the synchronous queue record.
User ID: Displays the User ID of the person who has initiated the request.
Event date: Displays the date that the data record became effective from a business point of view. The event date and time are the actual date- and timestamps when the data record is created as an synchronous request.
Result code: Displays the result code which is provided by the STCDS when the data is uploaded to or downloaded from the data server.
Tip: The ToolTip of this cell will display the result code including the description, if available.
Grid Shortcut Menu on Synchronous Requests tab:
Open: Maintains the selected synchronous data record.
Displays all communication type details. After entering the filter details, the grid is refreshed with the communication type details that meets the filter.
Filters on Communication Types tab:
Direction: Select to filter the displayed grid details on the direction of the data transfer, for example:
[Blank]: Displays all available data transfer requests for the selected External system ID.
Inbound: Displays the requests for data received from the STCDS.
Outbound: Displays the requests for data sent to the STCDS.
Synchronous: Displays the requests initiated by Autoline, Autoline will sent data to the STCDS and a response is received instantly.
Processing module: Select to filter the displayed grid details on the processing module that contains the actual processing operations, for example:
[Blank]: Displays the configured processing modules for the selected External system ID.
MS/MBASM: XENTRY Portal pro interface
MS/MBCAS: CAS interface
MS/MBGCM: GO in CESAR Order replication
MS/MBIBI: IBIS interface
MS/MBMEM: MBC Retail Tablet interface
MS/MBPEV: EVA - Gala 1 (RAR) interface
MS/MBPGO: WIN GO - Vehicle ordering
MS/MBPOM: MBC POS OOM - Offer and Order Management
MS/MBPSM: MBC POS LMS - Lead management interface
MS/MBPVM: PVS Interface
MS/MBVDF: VDF - Franchise data import
Grid on Communication Types tab:
The available communication types are grouped by the available processing modules.
[Icon]: Displays the icon that indicates the direction of the data transfer for the concerning communication type.
: Inbound request, the data is received from the STCDS.
: Outbound, the data is sent to the STCDS.
- blue arrow right, grey arrow left: Synchronous request initiated by Autoline, Autoline will sent data to the STCDS and a response is received instantly.
Type: Displays the type of the communication as configured by the StarConnect Data Server function or any other related topics, for example:
- Xentry Portal pro:
- SERVICE_JOB
- CAS:
- CAS_CUSTOMER_BATCH_CHECK
- GO in CESAR Order replication:
- CS_ORDER
- CS_PRE_ORDER
- CS_PRE_ORDER_CONFIRMATION
- CS_RETAILDATE
- IBIS:
- ACCOUNTING_ENRICHMENT_REPLY
- ACCOUNTING_ENRICHMENT_REQUEST
- REPURCHASE_RESALE_DATA
- MBC Retail Tablet:
- CAR_CONFIG
- EVA - Gala 1 (RAR):
- GALA1_REQUEST
- WIN GO - Vehicle ordering:
- PC_ORDER
- PC_REPORTING
- MBC POS OOM - Offer and Order Management:
- PC_RETAIL_ORDER
- MBC POS LMS - Lead management:
- ERROR_COMPANY
- ERROR_CONTACT
- ERROR_LEAD_CANDIDATE
- ERROR_PERSON
- LEAD_CANDIDATE
- PERSON
- PVS:
- USED_VEHICLE
- USED_VEHICLE_MARKET_PLACE
- USED_VEHICLE_MASTER_DATA
- VDF - Franchise data import:
- PC_MASTER_DATA
Description: Displays the description of the use for the communication type. This description is also included in emails that are sent when receiving and sending data.
Active: Displays if the communication type is active.
Schedule: Displays the schedule information for automatic processing.
Last communication: Displays the date and time the last communication request of this type is done.
Result code: Displays the result code which is provided by the STCDS when the data is uploaded to or downloaded form the data server.
Tip: The ToolTip of this cell will display the result code including the description, if available.
Grid Shortcut Menu on Communication Types tab:
New: Creates a communication type record ready for you to complete.
Tip: Please consider to use the Add Default Communication Types function to create all relevant communication types automatically.
Note: This option is only available for Autoline users with a priority level of 7 or higher.
Edit: Maintains the corresponding communication type record.
Note: The Communication types form is only maintainable for Autoline users with a priority level of 7 or higher.
The communication daemon handles all the communication requests (inbound and outbound) in the background. You can start the communication daemon manually via the Menu Bar and Toolbar of Communication Module form or automatically via Timed operations.
Tip: You can setup the communication daemon function to start and stop the daemons automatically in Timed operations with module MS and option MBMDSSDS (StarConnect data server).
You can also use the Start All Backgrounds function manually or automatically in Timed operations with module SU and option STARTALL (Start all backgrounds), so that the Mercedes-Benz Daemon Monitor is triggered to start all concerning Mercedes-Benz daemons.
Inbound communication requests are executed based on the configured Communication Types and the schedule information within these communication types. The communication daemon will automatically place a request at the data server for retrieving new outstanding data from the data server.
Data received from the data server can be processed directly after receiving. The processing module as specified on the inbound communication type record is called to process the retrieved data. In case of:
Failure: An inbound queue record is created with status New, if no processing module is specified or the processing module could not process the retrieved data.
Success: The data in the inbound queue is stored with status Processed if the data is directly processed by the specified processing module. An email, containing the information of the inbound request record, is send to the user specified in the Inform on success field on the Communication Types form.
The timestamp of the last attempt to retrieve new data from the data server is stored in the Last run fields of the Communication Types form. This date and time is included in the next request that is send to the data server. The data server will use this to select the outstanding files since the previous fetch.
Outbound communication requests are transmitted to the data server shortly after the process that generated the request has stored the request in the outbound queue of the StarConnect data server communication module and the schedule information on the corresponding communication type record allows transmitting the data. In case of:
Failure: An email, containing the details of the communication problem, is send to the user specified in the Inform on failure field on the Communication Types form and/or the System manager email of the StarConnect Data Server Parameters. A new attempt to send the file is done within one hour after the failure this will continue every hour until the connection problems are solved. The email is only sent once, on the moment of the first attempt of transmitting the data.
Success: An email, containing the information of the outbound request record, is send to the user specified in the Inform on success field on the Communication Types form.
The timestamp of the last attempt to transmit data to the data server is stored in the Last run fields of the Communication Types form.