Abstract: A method, system, and computer program product that is configured to: receive inbound data; tag a plurality of data fields of the inbound data; execute at least one integration flow which transforms the inbound data with tagged data fields to transformed data with the tagged data fields; obscure values of the data fields in the transformed data based on the tagged data fields; and send outbound data which includes the transformed data with the obscured values of the data fields.

Abstract: A method, computer program product, and computer system are described for providing integration flows between endpoint systems. The method includes providing a delegation integration module for each of multiple disparate types of endpoint systems, wherein a delegation integration module for a type of endpoint system is configured to understand how to construct and coordinate integration artifacts in the endpoint system type. The method includes defining an integration flow with required endpoint systems. This integration flow includes generating required linked integration artifacts, injecting the integration artifacts into the relevant endpoint systems that are ready for execution, delegating integration tasks of the integration flow via the delegation integration modules to the required endpoint systems, and using the linked integration artifacts at the endpoint systems to carry out the integration tasks.

Abstract: An integration flow can be improved with the use of a pattern identified from a pattern library. The identified pattern can include a snippet of nodes which are functionally equivalent to a subset of nodes in the integration flow. The pattern also lists an endpoint capable of performing the snippet of nodes. The integration flow can therefore be updated to cause the endpoint to perform the snippet of nodes.

Abstract: A sensor assembly includes a sensor including a sensor lens, a casing mounted to the sensor, and a fluid nozzle mounted to the casing. The casing at least partially defines a duct positioned to outlet airflow across the sensor lens, and the duct defines a direction of airflow. The fluid nozzle is aimed through the duct in the direction of airflow.

Abstract: An integration flow can be improved with the use of a pattern identified from a pattern library. The identified pattern can include a snippet of nodes which are functionally equivalent to a subset of nodes in the integration flow. The pattern also lists an endpoint capable of performing the snippet of nodes. The integration flow can therefore be updated to cause the endpoint to perform the snippet of nodes.

Abstract: The invention relates to a sample collection system for collecting sub-samples from a material stream, the system including a valve arrangement and a static cone splitter, and wherein the valve arrangement is arranged to enable operation of the static cone splitter to collect a non-biased sample of the material stream fed to the static cone splitter under first and second operational conditions, the first operational condition requiring the material stream to be at substantially atmospheric pressure and flowing at a minimum functional flow rate, and the second operational condition requiring the material stream to be pressurised above atmospheric pressure and at a flow rate higher than the minimum functional flow rate. The invention also relates to a static cone splitter for use with the system, together with a cone member for use with the static cone splitter.

Abstract: A computer-implemented method for a multi-tenant integration environment includes, in response to an error occurring during a state of execution of an integration flow, generating error data for the error. The method further includes associating the generated error data with the error. The method further includes storing the generated error data in a data storage component. The generated error data includes (i) error state information corresponding to the state of execution of the integration flow and (ii) target state information corresponding to a target state of execution of the integration flow.

Abstract: A sensor assembly includes a sensor including a sensor lens, a casing mounted to the sensor, and a fluid nozzle mounted to the casing. The casing at least partially defines a duct positioned to outlet airflow across the sensor lens, and the duct defines a direction of airflow. The fluid nozzle is aimed through the duct in the direction of airflow.

Abstract: A computer-implemented method for a multi-tenant integration environment includes, in response to an error occurring during a state of execution of an integration flow, generating error data for the error. The method further includes associating the generated error data with the error. The method further includes storing the generated error data in a data storage component. The generated error data includes (i) error state information corresponding to the state of execution of the integration flow and (ii) target state information corresponding to a target state of execution of the integration flow.

Abstract: Presented are concepts for configuring data communication with an application flow in an integration system, wherein various connection routes to an application flow may be offered to a client. By way of example, connection configuration information associated with an application flow may relate to a plurality of different connection routes that are available for the associated application flow. This connection configuration information may be dynamically maintained to reflect flow and connection route availability. When an application flow is requested by a client, the connection configuration information for that application flow may be provided to the client. This may enable the client to select a preferred route.

Abstract: Presented are concepts for configuring data communication with an application flow in an integration system, wherein various connection routes to an application flow may be offered to a client. By way of example, connection configuration information associated with an application flow may relate to a plurality of different connection routes that are available for the associated application flow. This connection configuration information may be dynamically maintained to reflect flow and connection route availability. When an application flow is requested by a client, the connection configuration information for that application flow may be provided to the client. This may enable the client to select a preferred route.

Abstract: The invention relates to a sample collection system for collecting sub-samples from a material stream, the system including a valve arrangement and a static cone splitter, and wherein the valve arrangement is arranged to enable operation of the static cone splitter to collect a non-biased sample of the material stream fed to the static cone splitter under first and second operational conditions, the first operational condition requiring the material stream to be at substantially atmospheric pressure and flowing at a minimum functional flow rate, and the second operational condition requiring the material stream to be pressurised above atmospheric pressure and at a flow rate higher than the minimum functional flow rate. The invention also relates to a static cone splitter for use with the system, together with a cone member for use with the static cone splitter.

Abstract: While a device is offline, usage data is tracked on the device. The usage data is uploaded to a server after the device is again connected to a network. Applications that run on mobile devices typically embed a browser to display content. Unfortunately, mobile devices also frequently disconnect from the associated network. A system tracks usage data by using JavaScript in the browser to communicate with the native device, which then buffers the usage data for future upload. This is done by installing, in each application, a “protocol handler” that listens for a request over a particular protocol. The protocol handler intercepts the requests and stores the usage data locally on the device. Subsequently, when the device detects network connectivity, the device uploads the data to servers that collect data for aggregation and presentation.

Abstract: Embodiments presented herein provide methods, systems and computer program products for determining a count of network users. One method identifies one or more login access requests, from one or more server logs. Each of the one or more login access requests comprises a login cookie, and a user identifier. The method then forms one or more connected components based on the one or more login access requests. Each connected component comprises one or more user identifiers, wherein each of the one or more user identifiers is associated with one or more login cookies. The method finally determines a count of login users based, at least in part, on the user identifiers in the one or more connected components.

Abstract: While a device is offline, usage data is tracked on the device. The usage data is uploaded to a server after the device is again connected to a network. Applications that run on mobile devices typically embed a browser to display content. Unfortunately, mobile devices also frequently disconnect from the associated network. A system tracks usage data by using JavaScript in the browser to communicate with the native device, which then buffers the usage data for future upload. This is done by installing, in each application, a “protocol handler” that listens for a request over a particular protocol. The protocol handler intercepts the requests and stores the usage data locally on the device. Subsequently, when the device detects network connectivity, the device uploads the data to servers that collect data for aggregation and presentation.

Abstract: Embodiments presented herein provide methods, systems and computer program products for determining a count of network users. One method identifies one or more login access requests, from one or more server logs. Each of the one or more login access requests comprises a login cookie, and a user identifier. The method then forms one or more connected components based on the one or more login access requests. Each connected component comprises one or more user identifiers, wherein each of the one or more user identifiers is associated with one or more login cookies. The method finally determines a count of login users based, at least in part, on the user identifiers in the one or more connected components.