Use the following guidelines to ensure that all customized scripts execute successfully.
- Examine any iScript that relies on machine-specific settings. For example, if you have a script
that performs an ODBC lookup, you must also install and configure the ODBC drivers
on the test server. Check any paths that are located in scripts that reference the
file system and ensure they are valid paths on the test server. Note that UNIX does
not support the COM interface, so if you are moving from Windows to UNIX and have
scripts with COM objects, you must find alternatives.Note: If any script alters data outside of Perceptive Content, create a test environment for that application.
- If you use Perceptive Content Printer, determine the server-side printing scripts that you need to copy and ensure that all scripts reference a print INI file from the correct directory.