Method for accessing business object resources and machine-to-machine communication environment

摘要

A consumer application e.g. an Enterprise Resource Planning (ERP) system subscribes S100 to a provider business application (e.g. a supplier lifecycle management (SLM)) system hosting business object resources to which business events, e.g. updates in supplier information, are assigned S110. A uniform resource identifier (URI) identifying a business object resource S130 affected by an occurring business event is included in a message generated by an event message generator S140 and sent to all subscribing customer applications via a message broker S150. The consumer application only connects to the business object resource via a RESTful API if it determines the message is of interest based on the URI S170. The message broker may be embedded in stand-alone message-orientated middleware (Figure 2), or be embedded in the provider business application, sending messages directly to the consumer applications (Figure 1) or via middleware (Figure 3). The event message may include a hyperlink and content type information of the affected business object resource. Different versions of the business object resources may be assigned different HTTP content type headers, a standard content type header being used to call the newest version of the business object resource. The message may be a JMS message. An event driven model is used for fetching business information rather than relying on requests from the customer application and a secured web application e.g. single sign on can be used as polling is not necessary.