Facing issue in Deploying jobs in production .

[Former Member]

We export jobs from Development to Production by exporting and importing XML.

All the fields of DATA Store are override by development parameter like 'tns name', 'User Name','password'
Every time we have to reset password and connection property of DATA STORE .

Is there any method of export or import so that DATA Store property does not get override ?

Regards

Anupam

[former_member315492]

Hi,

Below are suggestions:

1.It is better to take separate backup of Datastores as .ATl files. After deploying .ATL file in to new environment, change creditentials like User name,password and TNS name ..... etc.

2. Through central repositories like check in and Check out functionality we can get the projects in to new environment

                                     OR

Take the backup of projects as .ATL files and import in to New environment.

3.Take the backup of substitution parameters and syastem configurations as .ATL file and import in to new environment.

I hope this will helps you to resolve the issue.

Regards,

Narasimha.

[Former Member]

Hi Narasimha,

Actually my problem is your Point No. 1 , I don't want to change password, TNS of existing Datastore of production .

for Example there is a Datastore in Production name APPS_DS , jobs are already  running in production.

When I am deploying jobs in production which are using APPS_DS then User name,password and TNS name are override by development User name,password and TNS name.

In between scheduled jobs get failed due to wrong user name and password .

I want to know any wok around by which I need not to change User name,password and TNS name in production .

[Former Member]

Hello

It is very easy to implement a process to overcome this, but many people still override the target environment!

First export - include everthing - jobs, workflows, dataflows, etc.  Once in target environment set datastore values.

Subsequent exports - exclude datastores, or use the option 'exclude envrionmental information'.  As long as dependant objects exisit in the target repository, the import will work.

Michael

[former_member315492]

Hi Anupam,

1. While taking back up of Jobs exclude datastores. so that while importing jobs, datastores not taken by the developments credentials.

2. After taking backup of datastores  as .ATL  file, Change the credentials of Production instead of production.

Regards,

Narasimha.

[DayaJha]

Hi Anupam,

Please follow the below steps for deployment of ATL Backup from One Environment (Development) to Other Environment (Production), If you are using data quality or data services or any parameter then only change the Substitution Parameter from One Environment to Other.

• Complete Backup of Project of BODS 4.X (Development) in form of ATL or XML
• System Configuration Backup of BODS 4.X (Development) in form of ATL or XML
• Substitution Parameter Backup of BODS 4.X (Development) in form of ATL or XML
• Deploy (ATL or XML) Complete Backup of Project of BODS 4.X (Development) to BODS 4.X (Production)
• Deploy (ATL or XML) System Configuration Backup of Project of BODS 4.X (Development) to BODS 4.X (Production)
• Deploy (ATL or XML) Substitution Parameter Backup of Project of BODS 4.X (Development) to BODS 4.X (Production)

Thanks,

Daya

[kiran2509]

Hey Daya

Can you please explain how can we export 'system configurations' /parameters seperately

[DayaJha]

Hi Kiran,

Please refer the below thread.

Links:

http://scn.sap.com/thread/3433233

http://scn.sap.com/message/13921473#13921473

http://scn.sap.com/message/14666098

http://scn.sap.com/thread/3321158

Thanks,

Daya