Data source models are generally the source of data for a data service response or the target of data passed in a data service request, although mapping may result in data from one data source being persisted in another. Common Model : DataXtend SI enables you to build a loosely-coupled system by integrating data using a common model architecture. In this architecture, you map Data service and Data source schemas through a common model. A common model abstraction decouples components, simplifies mapping, and provides the most efficient exchange of data at runtime. Without a common model, integration is usually accomplished by means of point-to-point transformation. Runtime Configuration and Environment : Since development and testing environments usually differ from production environments, you can define different runtime environments for testing within the SI Workbench and for deployment. You can reuse the same runtime configurations, but use specific source locations that might be different within a deployment environment than they are within testing. Runtime Configuration: Runtime Configuration elements specify the data sources that a data service can access (the Data Sources tab) and the transaction mode. In a runtime configuration element, the following transaction modes are available: Local — The DataXtend SI runtime will manage the transaction. Distributed local — For use when the data services are not participating in a containing transaction Distributed global — For use when the data services are participating in a containing transaction as a session EJB.
Runtime Environment : A Runtime Environment element is a logical container for a set of Data Source Location elements. When you import schemas that contain connection information such as from a relational database or WSDL, the SI Workbench creates a Data Source Location . It enters this element in the Runtime Environment.
Each instance represents one environment in which data services will be run, such as during testing or deployment. The DataXtend SI runtime can connect to transactional data sources using one of the following Data Source Location connection types. JDBC Data Source — DataXtend SI manages the transaction. JNDI Data Source — The application server creates the connection so that the Java EE transaction manager can manage the transaction. Figure shows where we can choose the Data Source Location type. Rule Configurations: It contains one or more elements that specify whether to enforce validation rules and/or to skip one or more categories of rules during execution. When
You've reached the end of your free preview.
Want to read all 20 pages?
- Winter '16
- Willy Brown
- XML Schema