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; } } }

Location and Upgrade of custom scripts in 6.5

Tim__D

I'm upgrading to 6.5 and need to know the following.

Our custom callout CGI and .IPL callout files are in \iw-home\httpd\iw-bin. To ensure that we are observing all best practices what is the proper location for these types of custom scripts and why? What about inlines?

Our custom Perl modules have been moved to \iw-home\iw-perl\site\lib. Is this correct and do I need to re-install them or just copy and paste. We're running windows.

Any and all info / links to other posts related to upgrading inlines, callouts to work in 6.5 would be appreciated. I've been through the documentation but need more info.

Edited by Tim__D on 11/09/05 11:37 AM (server time).

Find more posts tagged with

Comments

jbonifaci

Custom CGI scripts should be located in

/iw-home/httpd/iw-bin/ClientName/.
Custom IPL scripts should be located in

/iw-home/custom/ClientName/.
Custom Modules should be located in

/iw-home/iw-perl/site/lib/ClientName/.

Basically, any files that can be located in an arbitrary location should be located somewhere under

/iw-home/custom/ClientName/. Any files that need to be within a specific directory (CGI/PM/JS) should be located in a sub folder called 'ClientName' beneath the directory they are required to be within.

~Jeff

QA_SWAndRefTblVer.rptdesign

QA_BadInspectionRecords.rptdesign

Tim__D

Thanks for the information. Where is the prefered location for workflow scripts /custom as well?

Also after the 6.5 install I see many .old directories. Are those created by the installation?

jbonifaci

Well, wft files should be put in

/iw-home/local/config/wft/ClientName.

The external tasks for the workflow files should be in

/iw-home/custom/ClientName/ or somewhere there under.

~Jeff

Adam Stoller

<font color='blue'>Custom CGI scripts should be located in

/iw-home/httpd/iw-bin/ClientName/.</font>

I'm not sure about now, but in the past putting CGI scripts in sub-directories of httpd/iw-bin didn't work unless you created some sort of wrapper script that lived in httpd/iw-bin (this was partially for custom menus, but I think mostly for cgitask scripts)

I've generally used httpd/iw-bin/****_scriptname.ipl - where '****' is some organizational / client abbreviation name - thus ensuring that all such custom files show up together in directory listings (that are sorted alphabetically) and/or are otherwise easy to identify.

So - if you can use sub-directories for the customer - it's generally a good idea to do so; if you cannot use sub-directories (and sometimes even if you can) - using an identifiable prefix string for the filenames is the next-best-practice.

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

jbonifaci

Adam,

I recall having issues with this too a long time ago, but I've been using sub directories in iw-bin for the last 3 years in both 5.5 and 6.1 and have not had any issues.

~Jeff

nipper

It did happen in 5.5.1. Scripts would run but not all the variables were available. I tried
it with showenv and got a restricted amount of data.

As you said, it does not matter anymore as it seems to work fine in 6.X

jbonifaci

Ah, well, maybe I didn't rely on those variables in 5.5 and just didn't notice,

Tim__D

Adam,

I recall having issues with this too a long time ago, but I've been using sub directories in iw-bin for the last 3 years in both 5.5 and 6.1 and have not had any issues.

~Jeff

I've now started the upgrade and I'm getting an apache error unless the scripts are located in the httpd/w-bin root directory?

How can I get apache to look in subdirectories as well? httpd/w-bin/companyName/FormsPublisher etc.....

Tim__D

The error was due to permission issues. I have another issue but thats likely a separate thread.