Abstract: A conveyor chute is suitable for use as a store for goods, such as packages and pieces of luggage. The conveyor chute has at least one sliding section with an inclined sliding surface with a direction of fall along the sliding surface as well as a sliding width. The sliding section has a width adjusting mechanism which allows the goods to be distributed across at least part of the sliding width and which thus allows the conveyor chute to be used in an improved manner for storing the goods.

Abstract: An optoelectronic sensor (10) is provided for detecting object information from a monitored zone (12) having a light receiver (24); a reception optics (22) associated with the light receiver (24) for generating a light spot on the light receiver (24); and an evaluation unit (26) for generating the object information from a received signal of the light receiver (24). In this respect, a manipulation unit (30) is provided to vary the reception optics (22), the light receiver (24) and/or elements of the reception optics (22) such that the portion of the light spot that is incident on the light receiver (24) varies.

Abstract: An optoelectronic sensor (10) for monitoring a monitoring region (12), the sensor (10) comprising an image sensor (16a-b), an illumination unit (20) for at least partially illuminating the monitoring region (12) with an illumination field (26), an illumination control (28) configured for a power adaption of the illumination unit (20) for meeting safety requirements, and an additional distance-measuring optoelectronic sensor (38) for detecting the distance at which an object (42) is located in the illumination field (26), wherein the illumination control (28) is configured for a power adaption in dependence on the distance measured by the additional sensor (38).

Abstract: An optoelectronic apparatus for securing a source of danger in a spatial zone includes at least one image sensor that works in the infrared spectrum and that can generate range-resolved data of the spatial zone as well as an evaluation unit that is configured for the evaluation of the data for the detection of objects in a three-dimensional protected space within the spatial zone, wherein the source of danger is additionally at least partly secured by a mechanical partition that is at least very largely permeable to visually visible light. To provide a solution that prevents or at least reduces disturbing optical influences from outside the partition, it is proposed that the partition is coated with a layer such that the non-coated layer that is at least partly transparent for the image sensor is visible for the image sensor in a defined manner through the layer and is opaque.

Abstract: A system and method for filtering messages in a messaging system is described. The system includes a user interface configured to receive user input for defining one or more message filters. Each message filter specifies predefined criteria by which a message is to be stopped. The system further includes a filter module comprising the one or more filters, and a queue connected with the filter module for queuing messages stopped according to one of the one or more filters. In a method, messages in the messaging system are stopped according to predefined criteria. Stopped messages are restarted according to a job executed by the messaging system.

Abstract: Systems and techniques are disclosed for transmitting a message through an application integration system without having to convert the message from a format that native to both a sending application and a receiving application. A computer-implemented method for transmitting a message from a sending application through an application integration system can include determining a receiving application of the message, and determining a file format used by the receiving application. If the file format used by the receiving application is substantially identical to a file format used by the sending application, the method can include wrapping the message in a markup language file envelope according to a markup language used by the application integration system. The message can then be routed in the markup language file envelope to the receiving application.

Abstract: A monitoring “cockpit” for a message exchange system is presented. In general, the monitoring cockpit provides a set of aggregated views in a graphical user interface that present a direct and intuitive overview of the entire message exchange system. These views provide information about the current state of the message exchange system, of the alerts that have occurred in the system, and of the current state of messaging with performance data of messaging included. From these views, a drilldown function is provided for more detailed views. The monitoring cockpit is designed as a central tool to quickly get an overview of the overall state of a productive message exchange system, allow a user to analyze problems in detail by navigating to the detailed status information, and repair problems by giving links to the appropriate message exchange configuration and administration tools.

Abstract: A computer-implemented method, computer program product, and system for monitoring messages being exchanged at runtime between two or more applications via a message exchange infrastructure are presented. A scenario definition for one or more messages is provided, the scenario definition including a number of scenario conditions that are associated with a set of scenario attributes related to the message header and/or message payload. A message format of the one or more messages is enriched at runtime with an associated set of scenario attributes.

Abstract: A manufacturing mold for the production of a rotor blade for a wind turbine, where at least in one region of its longitudinal extension between a rotor blade root and a rotor blade tip, the finished rotor blade has an aerodynamic cross-sectional profile that has a profile leading edge (nose) and a profile trailing edge which are connected together via a suction side and a pressure side of the cross-sectional profile. A manufacturing mold can be divided along at least one separation plane which extends in the longitudinal direction of the rotor blade and between the profile leading edge and the profile trailing edge while simultaneously dividing the suction side and the pressure side, into a manufacturing mold part for producing a rotor blade part having the profile leading edge, and into a manufacturing mold part for producing a rotor blade profile part having the profile trailing edge.

Abstract: Methods and apparatus, including computer systems and program products implementing a messaging protocol. The messaging protocol may be a messaging protocol for transporting a message across a messaging landscape in a collaborative network. Techniques include sending a message that is defined to include a structured message header with information related to at least one component from a set of components defined by a protocol, including protocol version information in a message such that a component of a messaging landscape can interpret the message based on the version information, defining a message as one of a class of messages, end-to-end acknowledgement for messages, and security for headers and payloads of messages.

Abstract: Systems and techniques are disclosed for transmitting a message through an application integration system without having to convert the message from a format that native to both a sending application and a receiving application. A computer-implemented method for transmitting a message from a sending application through an application integration system can include determining a receiving application of the message, and determining a file format used by the receiving application. If the file format used by the receiving application is substantially identical to a file format used by the sending application, the method can include wrapping the message in a markup language file envelope according to a markup language used by the application integration system. The message can then be routed in the markup language file envelope to the receiving application.

Abstract: Methods and apparatus, including computer systems and program products implementing a messaging protocol. The messaging protocol may be a messaging protocol for transporting a message across a messaging landscape in a collaborative network. Techniques include sending a message that is defined to include a structured message header with information related to at least one component from a set of components defined by a protocol, including protocol version information in a message such that a component of a messaging landscape can interpret the message based on the version information, defining a message as one of a class of messages, end-to-end acknowledgement for messages, and security for headers and payloads of messages.

Abstract: Systems and techniques are disclosed for transmitting a message through an application integration system without having to converting the message from a format that native to both a sending application and a receiving application. A computer-implemented method for transmitting a message from a sending application through an application integration system includes determining a receiving application of the message, and determining a file format used by the receiving application. If the file format used by the receiving application is substantially identical to a file format used by the sending application, the method includes wrapping the message in a markup language file envelope according to a markup language used by the application integration system. The message is then routed in the markup language file envelope to the receiving application.

Abstract: Methods and apparatus, including computer systems and program products implementing a messaging protocol. The messaging protocol may be a messaging protocol for transporting a message across a messaging landscape in a collaborative network. Techniques include sending a message that is defined to include a structured message header with information related to at least one component from a set of components defined by a protocol, including protocol version information in a message such that a component of a messaging landscape can interpret the message based on the version information, defining a message as one of a class of messages, end-to-end acknowledgement for messages, and security for headers and payloads of messages.

Abstract: A system and method are disclosed for pseudo-synchronous communication in an asynchronous messaging network. The system includes a forward pipeline for transmitting asynchronous request messages from a sender system to the receiver system, and a backward pipeline for transmitting asynchronous acknowledgement messages from the receiver system to the sender system. Each acknowledgement message includes a reference to a request message and a result of an event associated with the request message.

Abstract: A computer-implemented method, computer program product, and system for monitoring messages being exchanged at runtime between two or more applications via a message exchange infrastructure are presented. A scenario definition for one or more messages is provided, the scenario definition including a number of scenario conditions that are associated with a set of scenario attributes related to the message header and/or message payload. A message format of the one or more messages is enriched at runtime with an associated set of scenario attributes.

Abstract: A messaging system may include a sender backend system, a receiver backend system, and one or more intermediate hubs. The backend systems and message hubs may have messaging software with different protocol versions. The messaging system is downward compatible such that messages routed from the sender backend system through intermediate message hubs are received by the receiver backend system with a protocol version compatible with that of the receiver backend system.

Abstract: A monitoring “cockpit” for a message exchange system is presented. In general, the monitoring cockpit provides a set of aggregated views in a graphical user interface that present a direct and intuitive overview of the entire message exchange system. These views provide information about the current state of the message exchange system, of the alerts that have occurred in the system, and of the current state of messaging with performance data of messaging included. From these views, a drilldown function is provided for more detailed views. The monitoring cockpit is designed as a central tool to quickly get an overview of the overall state of a productive message exchange system, allow a user to analyze problems in detail by navigating to the detailed status information, and repair problems by giving links to the appropriate message exchange configuration and administration tools.