Abstract: A computing system is provided, which is configured to instantiate a testing environment, define an extract, transform, load (ETL) pipeline within the testing environment, generate a test data set to be inputted into the ETL pipeline, generate assert data predicting an output of the ETL pipeline based on the generated test data set, input the test data set into the ETL pipeline to generate output data, compare the assert data to the output data, and validate the output data using the assert data to generate validation data.

Abstract: A dynamic customization system provides custom behavior for an application that has client code with an extensibility point and that has server code. An entity that uses the application provides a specification of custom behavior for the extensibility point to an extensibility server. The specification specifies an operation to perform after an occurrence of an extensibility event of the extensibility point during execution of the client code. A client executing the client code retrieves an indication of an extensibility server. The client then retrieves from the extensibility server a specification of the custom behavior for the extensibility point. After the occurrence of the extensibility event, the client sends to an operation server a request to perform the operation. The client may then receive from the operation server a response indicating the status of the request.

Abstract: To make a trusted web service call, a client application sends a series of messages to obtain tokens that allow service requests to pass through a service relay. The user obtains a first security token by providing the user's credentials. A second token is obtained from a trust broker that validates the first token. Both tokens are then sent with a service request to a service relay. The service relay validates the second token and then passes the first token and the service request to a connector service. The connector service validates the first token and passes the service request to a target back end service. The connector service acts as the user when communicating with the back end service. Service responses are routed back to the user through the connector service and the service relay.

Abstract: A system generates a first data set by executing, in response to occurrence of an event, a data flow configured with a property of a first object of a first data processing system to map the first object to a second object of a second data processing system. The system acquires additional information, including additional properties of the first object and data used by the first and second data processing systems to communicate with other data processing systems, from the first and second data processing systems to map the first object to the second object. The system generates a second data set having a format compatible with the second data processing system based on the first data set and the additional information and sends the second data set to the second data processing system. The system maps other objects using reconfigured data flows.

Abstract: To make a trusted web service call, a client application sends a series of messages to obtain tokens that allow service requests to pass through a service relay. The user obtains a first security token by providing the user's credentials. A second token is obtained from a trust broker that validates the first token. Both tokens are then sent with a service request to a service relay. The service relay validates the second token and then passes the first token and the service request to a connector service. The connector service validates the first token and passes the service request to a target back end service. The connector service acts as the user when communicating with the back end service. Service responses are routed back to the user through the connector service and the service relay.

Abstract: To make a trusted web service call, a client application sends a series of messages to obtain tokens that allow service requests to pass through a service relay. The user obtains a first security token by providing the user's credentials. A second token is obtained from a trust broker that validates the first token. Both tokens are then sent with a service request to a service relay. The service relay validates the second token and then passes the first token and the service request to a connector service. The connector service validates the first token and passes the service request to a target back end service. The connector service acts as the user when communicating with the back end service. Service responses are routed back to the user through the connector service and the service relay.

Abstract: A dynamic customization system provides custom behavior for an application that has client code with an extensibility point and that has server code. An entity that uses the application provides a specification of custom behavior for the extensibility point to an extensibility server. The specification specifies an operation to perform after an occurrence of an extensibility event of the extensibility point during execution of the client code. A client executing the client code retrieves an indication of an extensibility server. The client then retrieves from the extensibility server a specification of the custom behavior for the extensibility point. After the occurrence of the extensibility event, the client sends to an operation server a request to perform the operation. The client may then receive from the operation server a response indicating the status of the request.

Abstract: To make a trusted web service call, a client application sends a series of messages to obtain tokens that allow service requests to pass through a service relay. The user obtains a first security token by providing the user's credentials. A second token is obtained from a trust broker that validates the first token. Both tokens are then sent with a service request to a service relay. The service relay validates the second token and then passes the first token and the service request to a connector service. The connector service validates the first token and passes the service request to a target back end service. The connector service acts as the user when communicating with the back end service. Service responses are routed back to the user through the connector service and the service relay.

Abstract: To make a trusted web service call, a client application sends a series of messages to obtain tokens that allow service requests to pass through a service relay. The user obtains a first security token by providing the user's credentials. A second token is obtained from a trust broker that validates the first token. Both tokens are then sent with a service request to a service relay. The service relay validates the second token and then passes the first token and the service request to a connector service. The connector service validates the first token and passes the service request to a target back end service. The connector service acts as the user when communicating with the back end service. Service responses are routed back to the user through the connector service and the service relay.

Abstract: A relay component for a back office service creates an externally exposed REST service endpoint in front of the back office service. Instead of calling the back office service directly, REST service clients make REST service calls to the relay component using the HTTP protocol. The relay component coverts the data to XML format and sends it in a SOAP call to the back office service. The relay component receives the response from the back office service as a SOAP response that is converted to a REST message to be sent to the REST client.

Abstract: To make a trusted web service call, a client application sends a series of messages to obtain tokens that allow service requests to pass through a service relay. The user obtains a first security token by providing the user's credentials. A second token is obtained from a trust broker that validates the first token. Both tokens are then sent with a service request to a service relay. The service relay validates the second token and then passes the first token and the service request to a connector service. The connector service validates the first token and passes the service request to a target back end service. The connector service acts as the user when communicating with the back end service. Service responses are routed back to the user through the connector service and the service relay.