cancel
Showing results for 
Search instead for 
Did you mean: 

Password file required for commandline job execution?

Former Member
0 Kudos

Hi all,

It appears that I am unable to execute batch jobs through the commandline without using the password file option.

I have correctly generate the execution script files through the Data Services Management Console. I have reviewed the scripts and they all appear well formed with the correct parameters.

But when I generate the script and unselect the "Use Password File" option, I keep getting this error when trying to launch the job from the commandline:

(14.2.4.668) 04_24_2015 09:54:58 (7696): No DS Local Repositories Registred in CMS

(14.2.4.668) 04_24_2015 09:54:58 (7696): *** RWJL_EXIT called.

(14.2.4.668) 04_24_2015 09:54:58 (7696): *** ERROR: RWJobLauncher failed to connect to CMS. (BODI-1250220) [/code]

When I tick the "Use Password File" option - it all works fine. However, I have a need to use the "old style" approach where there was no such thing as a password file.

So the above errors happens on our SAP DS 4.2 SP4 test system that runs on Microsoft Windows and uses SQL Server 2012 as repository + CMS (IPS) database.

When I try this on the actual SAP DS 4.2 SP4 system that runs on Red Hat Linux Enterprise and uses Oracle 11gR2 as repository + CMS (IPS) database, I get this error:

04-17-2015 14:22:51     Specified CMS authentication is not available.

04-17-2015 14:22:51     ERROR(CCMSLogonManager::InitializeSession)

04-17-2015 14:22:51     RWJobLauncher failed to connect to CMS.

04-17-2015 14:22:51     RWJobLauncher return code: 180011

On our older versions of Data Integrator (down to 11.5.3) the commandline execution on both Windows and Linux always worked fine and never required the use for a password file (I don't think this option even existed back then).

I have a requirement to make this work WITHOUT the password file. I have consulted the technical manuals but I cannot find anything that indicates this shouldn't work. I also cannot find any SAP Note that indicates that there is a problem here.

Am I missing something here? Has anyone else ran into the same issue and errors - and if so,  could you please share how you resolved this?  At this stage, my next port of call is to raise a SAP Support incident but I want to make sure I have tried all options first before I reach out to support.

Accepted Solutions (0)

Answers (2)

Answers (2)

0 Kudos

Hi Erik,

Did you manage to resolve the issue?

Regards,

Sunil

Former Member
0 Kudos

Hi Sunil,

Yes we did - although I cannot remember exactly what we did differently, it was quite some time ago.

Regards,
Erik

former_member187605
Active Contributor
0 Kudos

User authentication (also for connecting to DS Designer) has been introduced in DS 4.0.

Former Member
0 Kudos

Yes I am fully aware of that - but there is nothing to indicate that the use of the password file is mandatory?

If this was made mandatory following the authentication changes in DS 4.x, then the use of the password file should not be optional in the Management Console.

former_member187605
Active Contributor
0 Kudos

I have exactly the same Windows configuration, using Enterprise authentication for acessing DS. When I run Export Execution Command with Use Password File unchecked, it generates the .bat and .txt file. The latter contains the password in encrypted form. There's no password file generated. That exactly matched your requirements, doesn't it?

Which authentication mechanism are you using?

Former Member
0 Kudos

We are using Enterprise at the moment. The problem is not in creating the script files but executing them.

When trying to execute the script files generated WITHOUT the password file, we are getting errors in relation to connecting to the CMS (or not being able to find the repository in the CMS - see my original post).

Executing the script files generated WITH the password file, it all works fine.

Looking at the way the scripts are generated without the password file (and thus contain the encrypted passwords) vs. the password file, it appears that a different encryption algorithm is used and that may be part of the problem.

Also the introduction of the CMS under DS 4.x is not the factor here since both scripts include the CMS reference parameter.

Former Member
0 Kudos

no, it has nothing to do with encryption

can you enable the JobLauncherDebugTrace in the %DS_COMMON_DIR%\conf\DSConfig.txt file under int section ? set the value to 1 from 0

execute the batch file

the following error mean, it's able to connect to CMS, but you have not registered any DS Local Repository on that CMS

14.2.4.668) 04_24_2015 09:54:58 (7696): No DS Local Repositories Registred in CMS

the following error mean, you are not using a supported authentication type , by default it's secEnterprise

04-17-2015 14:22:51     Specified CMS authentication is not available.

check if the CMS Server Name, user etc are correct

can you post the command line that is generated ? you can mask the sensitive information, like hostname, port, user, password etc.

Former Member
0 Kudos

Thanks Manoj.

You are exactly right, the script defaults to Enterprise authentication (-NsecEnteprise) where it should be using LDAP instead (-NsecLDAP) as the associated accounts are using LDAP authentication.

As the Management Console never asks for the authentication method when generating the execution scripts - will it inherit the authentication method that was used to authenticate with CMC (IPS) when logging into the DS Management Console? Or will it always default to Enterprise and will it require manual changing to the proper authentication type? (Windows AD, LDAP, SAP, etc?).

Former Member
0 Kudos

the CMS connection information that you see in the exported or scheduled command line is taken from the settings that you do in the CMS Connection link in the DS MC under Administrator -> Management, not from the user that you use for login to DS MC

by default that will be secEnterprise

update that connection and recreate the script and check if that works