Abstract: A computer-based system may be configured to collect metadata for each source and target defined for a data pipeline and formatting information (e.g., schemas, transformations, etc.) associated with each entity and field. During the definition of the pipeline, how the data will end up in the target may be defined, for example, by a user of the computer-based system via a GUI/interface and/or the like. Information (e.g., modification information, etc.) describing how the data will end up in the target may be defined, stored, and accessed to determine and/or track over which fields and entities are affected by the user-defined mutations and over which schemas. Lineage information (e.g., a genealogical tree, data lineage tracing, etc.) describing a data, version, and transformation may be generated and used to determine a source for a data record, how changes to the data record are related, how lineage evolved, and/or the like.

Abstract: Disclosed herein are system, method, and computer program product embodiments for implementing automatic taxonomy tags in an API microgateway. The API microgateway may receive a plurality of API requests for an API managed by a customer in a period of time and route the plurality of API request to an instance of the API according to a policy of the API. The API microgateway may aggregate metrics information related to the plurality of API requests. The aggregated metrics information may include request features, response features, policy features, and performance features. In response to a cluster of the metrics information corresponding to a tag in a tag prediction system, the aggregated metrics information may be labeled with the tag. The tag and the aggregated metrics information may be added to an access log and sent to the customer.

Abstract: A Version Control System (VCS) and methods having high availability, and combining the advantages of a centralized VCS while overcoming the limitations of centralized VCSs in a cluster environment. The system and method copes with failures of components in a cluster environment gracefully to guarantee uptime. The VCS and methods support high availability in a centralized VCS utilizing a plurality of repositories having a suitable architecture. In particular embodiments the architecture utilizes one or more of: Active-Passive repository replication; Active-Passive repository replication with automatic recovery; Active-Active repository replication; and hybrid model (Active-Active and Passive repository replication).

Abstract: A Version Control System (VCS) and methods having high availability, and combining the advantages of a centralized VCS while overcoming the limitations of centralized VCSs in a cluster environment. The system and method copes with failures of components in a cluster environment gracefully to guarantee uptime. The VCS and methods support high availability in a centralized VCS utilizing a plurality of repositories having a suitable architecture. In particular embodiments the architecture utilizes one or more of: Active-Passive repository replication; Active-Passive repository replication with automatic recovery; Active-Active repository replication; and hybrid model (Active-Active and Passive repository replication).

Abstract: Systems and methods for providing high level view tracking of changes in SCA artifacts are provided. A system comprises a project history tool executing on a computer, which includes an extensible model which maps artifacts to files.

Abstract: A system and method of creating and managing one or more business objects is provided. The method can include receiving a request to create a business object and presenting a first user interface that is used to create a business object. The user interface can include one or more fields that define attributes and methods in the business object. The method can further include presenting a second user interface that is used to add documentation information for the business object, and storing the business object. The attributes and methods of the business object can be stored in separate files.

Abstract: A system and method of creating and managing one or more business objects is provided. The method can include receiving a request to create a business object and presenting a first user interface that is used to create a business object. The user interface can include one or more fields that define attributes and methods in the business object. The method can further include presenting a second user interface that is used to add documentation information for the business object, and storing the business object. The attributes and methods of the business object can be stored in separate files.