Datasource | using in plain DCT

dolly1

Hi,

I am successfully able to use datasource in inline commands and this is helpful to populate the drop downs but I am just able to use it in workflow modeler custom instantiation DCT only and not in other form publisher DCT.

Can anyone please let me know if this is possible at all?

I want to use datasource in DCTs because if I use perl command in inline then I have to hard code the path of the perl script because $iw-home/relativePathOfPerlScript is not possible in the same. If I use datasource I do not have to hard code any path.

I am using teamsite 6.7.1 SP1.

Any pointers are appreciated.

Thanks.

Migrateduser

Hi, I am successfully able to use datasource in inline commands and this is helpful to populate the drop downs but I am just able to use it in workflow modeler custom instantiation DCT only and not in other form publisher DCT. Can anyone please let me know if this is possible at all? I want to use datasource in DCTs because if I use perl command in inline then I have to hard code the path of the perl script because $iw-home/relativePathOfPerlScript is not possible in the same. If I use datasource I do not have to hard code any path. I am using teamsite 6.7.1 SP1. Any pointers are appreciated. Thanks.

check the 6.7.2 supplement.. I think it outlines how it works in that (since it was not part of the 6.7.1 docs themselves, but in some release notes).. and I thought I read in the Release Notes for 6.7.1 SP1- Patch 4 something about this.. so it might depend on your patch level too. I have not tried it myself, but below is the section I was talking about.. does not seem to mention anything other than the datacapture..

* Bug ID TS-5168 TeamSite inline commands in DCT/PT run as servletd process owner (iwui) rather than the user. Platform(s): Generic --------------------------------- Important Note for Bug ID TS-5168 --------------------------------- used in this note is the output of iwgethome command, for example /usr/bin/iwhome Processing Scripts through "iwutild" service/daemon --------------------------------------------------- Users have been able to upload scripts to the server and call them from the form (for example, using an inline callout). Since unauthorized users could also call any script using a callout, this was a potential security issue. You can now control how inline callouts are executed. The format for issuing inline commands in data capture templates has changed to: The prefix can be one of the following: - CLT -- Run the CLT as the System user (default). - Datasource -- Use information from within TeamSite or from an external source, such as LDAP or a database. - utild -- Execute the inline command defined in the iwutild.cfg file via "iwutild" service/daemon. The prefixes are case-insensitive. To preserve behavior from TeamSite 6.7.1 SP1 and earlier releases do not modify any files after this patch installation. Use "utild" prefix to secure inline commands for TeamSite OS users. To do this, perform the following steps as described in the following sections: 1. Modify the iwutild.cfg file 2. Modify the data capture template 3. Modify the application_custom.xml file 4. Make changes effective Step 1. Modify the iwutild.cfg File ----------------------------------- In iwutild.cfg, add an entry similar to the following under the tag: impersonate="true" name="getLocations" path="\httpd\iw-bin\getLocations.ipl" script="\\iw-perl\bin\iwperl.exe"/> Each command entry in iwutild.cfg must be given a name, such as "getLocations" in the example. On the Windows platform, each of the inline call processes configured with "utild" prefix will show user information in the iwutild.log file. Step 2. Modify the Data Capture Template ---------------------------------------- In the data capture template, specify one of the following formats for the inline command: When you specify "CLT:" prefix or do not specify a prefix, the command line is executed. In the example above the command line is "/bin/cat /tmp/a /tmp/b". When you specify "utild:" prefix, the command name configured in iwutild.cfg is executed. In the example above the command name is "command_name" and it must be configured in iwutild.cfg. The iwutild.cfg file controls various tasks including executing commands on behalf of trusted clients with impersonation. Step 3. Modify the application_custom.xml File ---------------------------------------------- To set up TeamSite with specific prefixes for handling inline callouts, edit the application_custom.xml file (see the TeamSite User Interface Customization Guide). Specify the following information: value="prefix1, prefix2, ..." public="true"/> Where "prefix1, prefix2, ..." in a comma-separated list of valid prefixes listed above. The our of the box assumed default is: value="CLT,Datasource" To lock down security for inline callouts so all inline processing is done through command names defined in iwutild.cfg, specify: value="utild,Datasource" To disable all inline callouts, specify: value="none" or value=" " Step 4. Make changes effective ------------------------------ 4.1 Restart TeamSite server to make changes effective for "iwutild". /etc/init.d/iw.server stop /etc/init.d/iw.server start 4.2 Redeploy custom toolkit into the Content Center. /iw-perl/bin/iwperl /install/install_webapps.ipl -f content_center ---------------------------------------- End of Important Note for Bug ID TS-5168 ----------------------------------------