on 01-23-2015 12:32 PM
what is the system configurations in bods ??
Hi,
Each system configuration defines a set of data store configurations that you want to use together when running a job. You can define a system configuration if your repository contains at least one datastore with multiple configurations. You can also associate substitution parameter configurations to system configurations.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kishore,
In my experience, configurations are primarily used in migrating the Data Services components between environments.
For example, Connection1 may have three configurations - Development, Test and Production. Each of these configurations contains the database connection information for the respective platforms, and within each platform we can stipulate the default configuration in Data Services.
Without the use of configurations, whenever we migrate between environments, the connection details in the target environment would be overwritten with the connection details for the equivalent database in the source environment - although you can migrate and exclude connections it is preferable to use configurations.
Configurations can also contain substitution parameter values specific to each environment. When you execute or schedule the job, you can select which configuration to use at runtime.
Regards,
Ian.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
You can use system configurations to use the same data services repository for running a single job for different source and target systems. You can mix and match the source and target depending on your requirements using system configurations. This is very helpful in cases where you have to run the same Data Services job (batch/realtime) but using a different source or load into a different target.
For example if you have a source system that has two instances one each for UK and Australia, where the tables' structure and transformation logic are not changed but the source is different based on the country for which you are running the job, a system configuration will allow you to do this without having to change data store connection details each time you run for one country or another.
kind regards
Raghu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
98 | |
11 | |
11 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.