Calling FormAPI scripts from TeamSite server location

Hi,

We've recently moved from TeamSite 6.0 to 6.5SP2. Earlier we had our formAPI scripts being called from a different branch on the TeamSite server and we cant seem to replicate that behaviour in 6.5. Can anyone point out the error.

in TS 60
< script language="javascript"
location="webserver"
src="/iw-mount/default/main/salesmrktg/forms_catalog/WORKAREA/maintenance/templatedata/formAPI/ContentForm.js"
/ >

In TS 65 only when we changed src to point to iw folder does it work.
< script language="javascript"
location="webserver"
src="/iw/GetUserInfo.js"/ >

Does /iw-mount not work in 65?

Platform:TeamSite 65SP2 on Solaris 58

Find more posts tagged with

Comments

ISCBorisB

Does /iw-mount not work in 65?

It does work.
The following is an excerpt from FormsPublisher:FormAPI Developer’s Guide Release 6.5

You can use the webserver location type to access content that is on the same TeamSite
server but in a different location than the template type directory by using the /iw-mount URL prefix

kingtut

Hi,

I checked both 6.0 FormAPI guide and 6.5.0 FormAPI guide. The 6.0 guide shows the iw-mount usage for the formAPI include in the DCT but the 6.5.0 guide does not mention usage of iw-mount in the src location to include the formAPI script in the DCT. Can anyone on 6.5.0 SP2 confirm that iw-mount does work for 6.5.0 SP2?

ISCBorisB

Hi,

I checked both 6.0 FormAPI guide and 6.5.0 FormAPI guide...

Check again: FormsPublisher:FormAPI Developer’s Guide Release 6.5
Chapter 2 Using FormAPI
The DCT <script> tag
~Page 10
. . .
You can use the webserver location type to access content that is on the same TeamSite
server but in a different location than the template type directory by using the /iw-mount
URL prefix:
<script src="/iw-mount/default/main/SomeBranch/EDITION/SomeEdition/SomeDirectory/
hello.js"/>
. . .

kingtut

Hi Boris,

Following is pg 10 from FormAPI developers guide Release 6.5

You may specify a user script in either of two ways:
???? You can include the user script in the DCT in the < script > tag, as a CDATA section. This has the advantage that the code is always with the template definition and changes that affect both parts can be maintained in a single file.
???? You can keep your code separate from your DCT and point FormsPublisher to your file using the src and location attributes. This makes it easier to share the file across templates.
To place the code inline in a CDATA section, place the content within the XML CDATA markers, < ![CDATA[ and ]] >. For example, the following code opens an alert when the template is first loaded:
< ruleset name="TeamSite Templating" >
< itemref name="Address"/ >
< script >
< ![CDATA[
alert ("Hello, world!");
]] >
< /script >
< /ruleset >
Alternatively, you could save the script in a file called hello.js and specify its location using the src attribute. The actual location the src attribute points to may be anywhere on a webserver, in the same directory as the data capture template type definition, or somewhere else on the same TeamSite server. The value of the location attribute controls
how the src attribute is interpreted:
webserver The src attribute is the URL of the target, for example
http://myserver/mypath/hello.js. This is the default if the location attribute is not specified. template-type In this case, src specifies a location relative to the template type directory. So if hello.js lived alongside the DCT in:
/iwmnt/default/main/WORKAREA/user/templatedata/category/type/hello.js
then specifying < script location="template-type" src="hello.js" would be sufficient.
Multiple < script > tags are allowed, in which case their user scripts are loaded into the target frame successively.
Typically, a user script consists of a set of functions, usually with one initialization function.The last line of the user script usually includes a call registering this initialization function to

My developers guide is missing (iw-mount example) or was it removed from the 6.5 guide by IW?

ISCBorisB

My developers guide is missing (iw-mount example) or was it removed from the 6.5 guide by IW?

Not sure. My version is "tst.650.formapi.pdf", 966 KB, 2/8/2005 12:46 pm.

We do not use iw-mount for FormAPI libraries so I can not tell if it works.
If somebody knows more please share

kingtut

My version is "tst.650a.formapi.pdf" 1.14Mb 3/18/2005 12:17pm

Can support point out if they have removed this feature?

kingtut

IW helped get this resolved. To those who d like to know the cause of this behavior. First, iw-mount is supported in 6.5 SP2.
The issue was that apache webserver was not configured to resolve the filepaths by using alias. Here's the entry that shouldve been added to the /etc/apache/httpd.conf file.

Alias /iw-mount/ /.iwmnt/
< Directory "/.iwmnt" >
Options All
Order allow,deny
Allow from all
< /Directory >

Also httpd.conf should be configured for Port=81. Also check iw.cfg for customer_webserver_port=81.

You should have ur formAPI webserver location issue resolved. Thanx IW support.