Substitution Parameters

Where does the repository get its substitution parameters from? Today we had them messed up and were unable to correct them up till now.

After accidentally importing an ATL that contained a complete repository instead of just a project, we got an error with the Address Cleanse, stating that it could not locate the address dictionaries. Since we run the job server on a Linux system, we were surprised to read a windows file path in the error. The location is defined by a the substitution parameter $$RefFilesAddressCleanse, which can be viewed/changed in the Designer via Tools --> Substitution Parameter Configurations.

The only thing I could think of, was to export our projects, jobs, etc, and recreate the repository (we actually deleted the tables from Oracle). But still the substitution parameter $$RefFilesAddressCleanse pointed to a directory on the Windows client machine (the one the repo was created from). I would expect to see a Linux path there.

My questions:

[list]Where does the repo get these values from, as during its creation, it has no knowledge of what Job Server is going to be used? I thought it might have something to do with (re) synchronizing the repo with a Job Server from the Server Manager, but that did not have any effect.
[/list][list]What should be in these variables:

  • $$RefFilesAddressCleanse
  • $$RefFilesDataCleanse
  • $$RefFilesGeocoder
  • $$SamplesInstall
  • $$CertificationLogPath

when running a Linux back-end?[/list]


lamanp :netherlands: (BOB member since 2008-09-02)

Hi Paul,

Old one… Was this ever answered :slight_smile:

Cheers,
Shaz


Shazin :india: (BOB member since 2011-07-19)

That’s truly an old post, but unfortunately it has never been answered. As far as I can recall we have created a new repository to set things straight again.


lamanp :netherlands: (BOB member since 2008-09-02)

Yeh, but an interesting one if can be answered by one of the experts here.

Cheers,
Shaz


Shazin :india: (BOB member since 2011-07-19)

Make a good sense… I will try this out sooner and let you know…

Interim, you guys know that we can individually export the Substitution Parameters alone from one repository and pull that onto another…


ganeshxp :us: (BOB member since 2008-07-17)

You mean manually edit those one by one?

Thanks,
Shaz


Shazin :india: (BOB member since 2011-07-19)

LOL…

You are about to give me a kick…

Right-Click on the Local Object Library --> Repository --> Export Substitution Parameter Configuration and export it. You are done and ready for import into another repo!!!


ganeshxp :us: (BOB member since 2008-07-17)

Got it Thanks… :stupid: :wave:

Cheers,
Shaz


Shazin :india: (BOB member since 2011-07-19)

Looking for the ‘Like’ button… :smiley:


lamanp :netherlands: (BOB member since 2008-09-02)

Haha I need to find the actual solution also. Man you posted long long back huh?I missed it!!! :roll_eyes:


ganeshxp :us: (BOB member since 2008-07-17)

does this halp?
C:\Program Files\Business Objects\BusinessObjects Data Services\Admin\Repo\substitutions_configuration.atl


jlynn73 :us: (BOB member since 2009-10-27)

Pretty much. That should bring back the Substitution Parameters to the Installation default. You will lose whatever is configured!!!

Yes repo creation will take bunch of .atl files from that folder and create…As simple as that guys… :roll_eyes:


ganeshxp :us: (BOB member since 2008-07-17)

if you are on DS version earlier than 14.0 (DS 4.0) then I think you can get the ATL of the older version of sbvar_store object from AL_LANG and AL_LANGTEXT

SELECT * FROM AL_LANG WHERE NAME = ‘subvar_store’ will give you the object_id of the all the version of the substitution parameters

SELECT TEXT_VALUE from AL_LANGTEXT WHERE PARENT_OBJID = ORDER BY SEQNUM;

append all the rows from the output, this will give you the ATL of the substitution parameters for that version of the object, you could try importing this ATL

you can first try this on a clean repo for testing purpost before actually trying it out on actual repo

from DS 4.0, only the latest version is maintained in the local repo


manoj_d (BOB member since 2009-01-02)