BODS 4.x al_engine repository parameter files

[Former Member]

Hi

Has anybody used repository parameter files with BODS 4.2?

We used them routinely with 3.2 but under 4.2 if I create a parameter file using the al_engine "-gr" option then when I attempt to use it, using the "-yr" option, then I get the error message

Could not parse the password file: d:/Program Files (x86)/SAP BusinessObjects/Data Services/conf/xxx.prm

Comparing the 3.2 and 4.2 parameter files it looks like the 4.2 has 32 bytes prepended to it compared to the 3.2 version.

I have tried using a passphrase in the creation and use of the parameter file but get same error.

[Former Member]

from DS 4.0 onwards the password file doesn't store repo connection information, it only stored CMS connection (the connection information, that you register in DS MC -> Administrator -> Management -> CMS Connection)

why are you generating this file manually ?

if the password of repo is changed and updated in CMC, all the job schedules or exported execution commands will use that

[Former Member]

Hi Manoj

In 3.2 we generated a repository information file using al_engine as in

al_engine -S<servername> -NMicrosoft_SQL_Server -Q<dbname> -U -P -g -gr"xyz.prm"

this would create a file xyz.prm in %LINK_DIR%/conf. We could then use that file using the -yr option as in something like

al_engine -yr"xyz.prm" -X

Which mean that a) there was less typing and b) we did not have to expose the server and database name

My question was how I could achieve the same thing in 4.2 where al_engine -gr .... happily creates the xyz.prm file but then objects to the file when I try using it via the -yr option.

[Former Member]

from DS 4.0 onwards, this file doesn't store repository connection information, it stores CMS connection information

if you were using this file mainly for updating the repo connection, it's not required in DS 4.2, do you need the command line args for updating the CMS Connection in this file ?