Abstract: Techniques are disclosed for consuming and integrating with representational state transfer (REST) based services. In one embodiment, a multiple-step extract, transform, load (ETL) job includes one or more REST steps. Each step in the ETL job performs a particular well-defined task, and the REST step in particular constructs REST requests, invokes REST services, and retrieves REST responses. The REST step may be mapped to a vector of inputs such that multiple REST service calls are made for each of the inputs. Further, a reusable connection may be employed so that one connection can be used to make multiple REST service calls. URLs used to make REST service calls may be dynamically constructed based on input data parameters and ETL job parameters. Additionally, a graphical user interface (GUI) allows users to configure aspects of a REST step.

Abstract: Techniques are disclosed for consuming and integrating with representational state transfer (REST) based services. In one embodiment, a multiple-step extract, transform, load (ETL) job includes one or more REST steps. Each step in the ETL job performs a particular well-defined task, and the REST step in particular constructs REST requests, invokes REST services, and retrieves REST responses. The REST step may be mapped to a vector of inputs such that multiple REST service calls are made for each of the inputs. Further, a reusable connection may be employed so that one connection can be used to make multiple REST service calls. URLs used to make REST service calls may be dynamically constructed based on input data parameters and ETL job parameters. Additionally, a graphical user interface (GUI) allows users to configure aspects of a REST step.

Abstract: Techniques are disclosed for consuming and integrating with representational state transfer (REST) based services. In one embodiment, a multiple-step extract, transform, load (ETL) job includes one or more REST steps. Each step in the ETL job performs a particular well-defined task, and the REST step in particular constructs REST requests, invokes REST services, and retrieves REST responses. The REST step may be mapped to a vector of inputs such that multiple REST service calls are made for each of the inputs. Further, a reusable connection may be employed so that one connection can be used to make multiple REST service calls. URLs used to make REST service calls may be dynamically constructed based on input data parameters and ETL job parameters. Additionally, a graphical user interface (GUI) allows users to configure aspects of a REST step.

Abstract: Provided is a method for processing input data in a storage system and in communication with a repository. Views are generated that comprise a tree of nodes selected from a subset of nodes in a hierarchical representation of a schema. The views are saved to the repository. At least one of the views are used to create a job comprising a sequence of data transformation steps to transform the input data described by input schemas to the output data described by output schemas.

Abstract: Techniques are disclosed for consuming and integrating with representational state transfer (REST) based services. In one embodiment, a multiple-step extract, transform, load (ETL) job includes one or more REST steps. Each step in the ETL job performs a particular well-defined task, and the REST step in particular constructs REST requests, invokes REST services, and retrieves REST responses. The REST step may be mapped to a vector of inputs such that multiple REST service calls are made for each of the inputs. Further, a reusable connection may be employed so that one connection can be used to make multiple REST service calls. URLs used to make REST service calls may be dynamically constructed based on input data parameters and ETL job parameters. Additionally, a graphical user interface (GUI) allows users to configure aspects of a REST step.

Abstract: Techniques are disclosed for consuming and integrating with representational state transfer (REST) based services. In one embodiment, a multiple-step extract, transform, load (ETL) job includes one or more REST steps. Each step in the ETL job performs a particular well-defined task, and the REST step in particular constructs REST requests, invokes REST services, and retrieves REST responses. The REST step may be mapped to a vector of inputs such that multiple REST service calls are made for each of the inputs. Further, a reusable connection may be employed so that one connection can be used to make multiple REST service calls. URLs used to make REST service calls may be dynamically constructed based on input data parameters and ETL job parameters. Additionally, a graphical user interface (GUI) allows users to configure aspects of a REST step.

Abstract: Techniques are disclosed for consuming and integrating with representational state transfer (REST) based services. In one embodiment, a multiple-step extract, transform, load (ETL) job includes one or more REST steps. Each step in the ETL job performs a particular well-defined task, and the REST step in particular constructs REST requests, invokes REST services, and retrieves REST responses. The REST step may be mapped to a vector of inputs such that multiple REST service calls are made for each of the inputs. Further, a reusable connection may be employed so that one connection can be used to make multiple REST service calls. URLs used to make REST service calls may be dynamically constructed based on input data parameters and ETL job parameters. Additionally, a graphical user interface (GUI) allows users to configure aspects of a REST step.

Abstract: Provided is a method for processing input data in a storage system and in communication with a repository. Views are generated that comprise a tree of nodes selected from a subset of nodes in a hierarchical representation of a schema. The views are saved to the repository. At least one of the views are used to create a job comprising a sequence of data transformation steps to transform the input data described by input schemas to the output data described by output schemas.

Abstract: According to one embodiment of the present invention, a system decomposes a set of schema files. The system receives a set of schema files and automatically identifies a plurality of root schema files in the set, where a root schema file is determined based on remaining schema files in the set lacking a reference to that schema file. For each root schema file, the system creates a subset of the original set of schema files. The subset contains the root schema file, and at least one subset further includes one or more schema files that provide information for that root schema file. Embodiments of the present invention further include a method and computer program product for decomposing a set of schema files in substantially the same manners described above.

Abstract: Provided is a method for processing input data in a storage system and in communication with a repository. Views are generated that comprise a tree of nodes selected from a subset of nodes in a hierarchical representation of a schema. The views are saved to the repository. At least one of the views are used to create a job comprising a sequence of data transformation steps to transform the input data described by input schemas to the output data described by output schemas.

Abstract: According to one embodiment of the present invention, a system decomposes a set of schema files. The system receives a set of schema files and automatically identifies a plurality of root schema files in the set, where a root schema file is determined based on remaining schema files in the set lacking a reference to that schema file. For each root schema file, the system creates a subset of the original set of schema files. The subset contains the root schema file, and at least one subset further includes one or more schema files that provide information for that root schema file. Embodiments of the present invention further include a method and computer program product for decomposing a set of schema files in substantially the same manners described above.

Abstract: Provided are a computer program product, system, and method for processing schemas in a storage system. A presentation of a schema in a graphical user interface (GUI) is comprised of multiple type nodes in a tree structure. Each type node comprises a hierarchical arrangement of a plurality of nodes including group nodes including a plurality of nodes and content nodes providing values. First user input selects one of the type nodes in the schema for a view. Second user input selects one of the nodes in the selected type node in the schema for a view. Third user input selects a node in the schema to indicate a root node of the schema for the view. The view includes the root node and at least one sub node of the root node and is added as a child to the selected type node.

Abstract: Provided are a computer program product, system, and method for processing input data in a storage system and in communication with a repository. Views are generated that comprise a tree of nodes selected from a subset of nodes in a hierarchical representation of a schema. The views are saved to the repository. At least one of the views are used to create a job comprising a sequence of data transformation steps to transform the input data described by input schemas to the output data described by output schemas.

Abstract: Provided is a method for processing input data in a storage system and in communication with a repository. Views are generated that comprise a tree of nodes selected from a subset of nodes in a hierarchical representation of a schema. The views are saved to the repository. At least one of the views are used to create a job comprising a sequence of data transformation steps to transform the input data described by input schemas to the output data described by output schemas.

Abstract: Provided is a method for processing schemas in a storage system. A presentation of a schema in a graphical user interface (GUI) is comprised of multiple type nodes in a tree structure. Each type node comprises a hierarchical arrangement of a plurality of nodes including group nodes including a plurality of nodes and content nodes providing values. First user input selects one of the type nodes in the schema for a view. Second user input selects one of the nodes in the selected type node in the schema for a view. Third user input selects a node in the schema to indicate a root node of the schema for the view. The view includes the root node and at least one sub node of the root node and is added as a child to the selected type node.

Abstract: Provided is a method for processing input data in a storage system and in communication with a repository. Views are generated that comprise a tree of nodes selected from a subset of nodes in a hierarchical representation of a schema. The views are saved to the repository. At least one of the views are used to create a job comprising a sequence of data transformation steps to transform the input data described by input schemas to the output data described by output schemas.

Abstract: Provided are a computer program product, system, and method for processing input data in a storage system and in communication with a repository. Views are generated that comprise a tree of nodes selected from a subset of nodes in a hierarchical representation of a schema. The views are saved to the repository. At least one of the views are used to create a job comprising a sequence of data transformation steps to transform the input data described by input schemas to the output data described by output schemas.

Abstract: Provided are a computer program product, system, and method for processing schemas in a storage system. A presentation of a schema in a graphical user interface (GUI) is comprised of multiple type nodes in a tree structure. Each type node comprises a hierarchical arrangement of a plurality of nodes including group nodes including a plurality of nodes and content nodes providing values. First user input selects one of the type nodes in the schema for a view. Second user input selects one of the nodes in the selected type node in the schema for a view. Third user input selects a node in the schema to indicate a root node of the schema for the view. The view includes the root node and at least one sub node of the root node and is added as a child to the selected type node.