nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

inline callout - Help

Tim__D

I've developed an inline callout and I am having a strange problem with. I am calling this as an inline, getting some DB data and trying to populate a dropdown.

<inline command="D:\\iw-home\\iw-perl\\bin\\iwperl

\\iw-home\\httpd\\iw-bin\\inline_DB_Content.ipl"/>

The callout works I've viewed it on the command line and also printed the output to a log file. See log file content below:

<?xml version="1.0" encoding="UTF-8"?>
<substitution>
<option value="example_data_value" label="example_data_label" />
<option value="example_data_value" label="example_data_label" />
<option value="example_data_value" label="example_data_label" />
<option value="example_data_value" label="example_data_label" />
</substitution>

Instead of populating the dropdown I'm getting this error:

Templating Error Page
An internal problem was encountered trying to create a requirements object for type Dotcom/Test.

If I just print static option elements in the callout or remove the callout the template does not throw this error. Do you have any ideas why this might be happening? Any information you could provide is greatly appreciated.

Edited by Tim__D on 07/30/04 12:42 PM (server time).

Find more posts tagged with

Comments

Dwayne

Have you verified that the data coming from the DB is valid XML? That is, escape things like '<' and '&'. That's what's caused problems for me with this in the past.

--

Current project: TS 5.5.2/6.1 W2K

ProfessorX

post the snipet section from your datacapture.cfg

Thanks in advance!
WIN2K TS/TST 5.5.2 sp5; OD 5.6.0.1; DD 5.5.2
The Professor-

Tim__D

<select>
<inline command="D:\\iw-home\\iw-perl\\bin\\iwperl

\\iw-home\\httpd\\iw-bin\\inline_callout.ipl"/>
</select>

Migrateduser

For Oracle your script may have to set the environment variable ORACLE_HOME, for Windows it may have to set SYSTEMROOT. DCT inlines run in an environment that has been stripped of its environment (presumably for security issues), which is a lame hassle for everyone.

iwovGraduate

Try changing


<inline command="D:\\iw-home\\iw-perl\\bin\\iwperl \\iw-home\\httpd\\iw-bin\\inline_DB_Content.ipl"/>


<inline command="D:/iw-home/iw-perl/bin/iwperl /iw-home/httpd/iw-bin/inline_DB_Content.ipl"/>

Tim__D

If I run the callout from the Teamsite box command line it runs. I dont follow you. What are the steps I need to take?

Tim__D

Templating Error Page
An internal problem was encountered trying to create a requirements object for type Dotcom/Test.

Dwayne

You running from the command line isn't the same as the templating engine running it. As was pointed out, the "standard" environment variables aren't set when the templating engine runs it for you. So if your DB requires some environment variables (Oracle, especially) then you'll need to set them in the script.

You said you had a log of the result. If you've got a log of the output when it's run by the templating engine, rather than when you ran it from the command line, then I would suggest trying to place that output directly into the DCT where the <inline .../> tag is (without the <substitution> stuff, of course.) That will make sure that the data you're trying to put into the DCT is valid.

--

Current project: TS 5.5.2/6.1 W2K

Tim__D

Ok, I've chnaged the SQL to only take values I know wont have special characters. I've also placed the output of the log file into the DCT. Removing the inline command in place of the static options works. The DCT comes up fine?

Tim__D

Dynamic options still fail?

Templating Error Page
An internal problem was encountered trying to create a requirements object for type Dotcom/Test.

Dwayne

Did you make the change that iwovGraduate suggested, changing the \\ references to /?

At minimum, you should be using single \ characters, not double. XML doesn't escape characters with \ the way Perl does.

--

Current project: TS 5.5.2/6.1 W2K

Tim__D

yes - I made that change but still getting error

Templating Error Page
An internal problem was encountered trying to create a requirements object for type Dotcom/Test.

Tim__D

Migrateduser

Try this, run

iwdctacleval /path/to/datacapture.cfg

on the command line - that should either give you no error (which could mean the problem is with environment, such as variables) or a more detailed error message.

Are you using Oracle or another database?

Are you using System DSN or User DSN? Sometimes the problem is that the DSN on a Windows server is created in user DSN instead of system.

Tim__D

I have master access to the system and have an admin accout on the Teamsite server. We are using SQL and System DSN

Dwayne

OK. I suggest you do the following:

Put the dynamic command back into the DCT
IMPORTANT: delete the current log file, to make sure no old data is being cached
Attempt to load the template again. You should get the error
Reply to this message, and attach the newly generated log file, so that we can have some hope of diagnosing the problem

Current project: TS 5.5.2/6.1 W2K

Tim__D

I cleared the log file and tried to load the DCT. I received the error but nothing was written to the log file. I ran the .ipl from the command line and got the following. I've changed the actual data though Smiley Wink

<?xml version="1.0" encoding="UTF-8"?>
<substitution>
<option value="some_data" label="some_data" />
<option value="some_data" label="some_data" />
<option value="some_data" label="some_data" />
<option value="some_data" label="some_data" />
<option value="some_data" label="some_data" />
<option value="some_data" label="some_data" />
</substitution>

Adam Stoller

Please attach the script inline_DB_Content.ipl so that we can make some constructive suggestions on how to adjust things to either fix, or at least increase the depth of our knowledge regarding the problem you are running into.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Dwayne

Well, that certainly narrows things down. The fact that the log wasn't create would certainly indicate that the script is either failing to run at all, or it's aborting before it gets a chance to write to the file.

Is the script small enough that you could post it here? (Assuming there's nothing too proprietary there that we're not allowed to see)

Other things that I can think of (I don't think they're likely, though)

Try changing the iwperl to iwperl.exe
Ensure that the directory where the log file is being written is world-writable

Current project: TS 5.5.2/6.1 W2K

Tim__D

#!D:\iw-home/iw-perl/bin/iwperl
use TeamSite::CGI_lite;
use TeamSite::Config;
use DBI;

my $cgi = TeamSite::CGI_lite->new();
$cgi->parse_data();

# Production Database
my $dsn = "DSNNAME";
my $db_instance = "DSNINSTANCE";
my $db_user_name = "USERNAME";
my $db_password = "PASSWORD";

my $db = DBI->connect("dbi Smiley Surprised

DBC:$dsn","$db_user_name","$db_password");

my $SQL="use $db_instance";
$db->do($SQL);
my $sth = $db->prepare($SQL);
$sth->execute();

$SQL = qq{select THIS, THAT from TABLE where THIS like 'A%' and Status=1};

$sth = $db->prepare("$SQL");
$sth->execute();

my %contentKeys = ();
while (@row=$sth->fetchrow()) {
$contentKeys{"$row[0]"} = $row[1];
}

$sth->finish;
$db->disconnect;

my $xml = "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<substitution>\n";

foreach $key(sort keys %contentKeys) {
$xml .= "<option value=\"$key\" label=\"$contentKeys{$key}\" />\n";
}

$xml .= "</substitution>";

open (LOG, ">D:\\iw-home\\custom\\log\\inline.log");

print "$xml";

print LOG qq{$xml};
close LOG;

exit 0;

Tim__D

Change "iwperl.exe" Did not work still getting the error Smiley Sad

Migrateduser

Add something like this at the top of the script and load the DCT in the browser again:

BEGIN
{
if ( ! defined( ${ENV{'SYSTEMROOT'}} ))
{
${ENV{'SYSTEMROOT'}} = 'C:\\winnt';
}
}

Dwayne

As john suggested, try adding the SYSTEMROOT environment variable near the top of the script:


$ENV{"SYSTEMROOT"} = "C:\\WINNT"; # or whatever it is on your box

You might also try putting the whole block of stuff that does DB access into an eval block, to trap any errors.

You also don't need the CGI stuff. This isn't CGI code

--

Current project: TS 5.5.2/6.1 W2K

Edited by Dwayne on 07/30/04 02:07 PM (server time).

Tim__D

OK You guys are great. This is working now. Now my only issue is the special character thing. I can sort this out though.

If you don't mind let me know the best way to manage the DSN on the Teamsite server. None of the other calllouts have this explicitly declared and they work fine? They use formAPI though and are not inline commands not sure if this makes a difference?

Thanks Again - Tim