OS4X Enterprise - OS4X Webaccess configuration

The following configuration parameters, configurable in "Configuration" -> "OS4X Enterprise" influence the behaviour of OS4X Webaccess, the end user web interface for using OS4X Enterprise functionality.

Encrypt Webaccess session information?

DB configuration name:

webaccess_session_encrypt

If enabled, OS4X Webaccess saves the session information for the logged in user in the database encrypted. This increases the CPU load of the webserver.

Compress Webaccess session information?

DB configuration name:

webaccess_session_compress

If enabled, OS4X Webaccess saves the session information for the logged in user in the database compressed. This increases the CPU load of the webserver.

Don't show receive queue view?

DB configuration name:

webaccess_disable_recq

OS4X Webaccess can show the receive queue (without administrative capabilities) to the end-user in a stripped view, containing company name, progress information etc. If you don't want this, you can disable the rendering of this overview for every user.

Don't show send queue view?

DB configuration name:

webaccess_disable_sendq

OS4X Webaccess can show the send queue (without administrative capabilities) to the end-user in a stripped view, containing company name, progress information etc. If you don't want this, you can disable the rendering of this overview for every user.

Show incoming jobs without recipient?

DB configuration name:

webaccess_show_invalid_rec_jobs

Jobs without a valid recipient must normally be handled seperately, i.e. by routing them to a target destination. If you don't want to invest this administrative overhead, you can give users of OS4X Webaccess the possibility to view incoming jobs without recipient. They can handle the job as a normal receive job, including fetching files, forward this job etc.

Session timeout

DB configuration name:

webaccess_session_timeout

After this configured timeout (in minutes) OS4X Webaccess removes stale sessions of logged in users.

Highlight address code in ENGDAT filenames?

DB configuration name:

webaccess_highlight_addresscode

If a filename is not converted to a human-readable filename (i.e. if the sender didn't define it in an ENGDAT abstract file), the filename can be hard to read. In order to increase the readability of the address code of the file (which defined the recipient of the file), it can be highlighted in the following ways:

• bold

DB configuration name:

webaccess_highlight_addresscode_bold

• underlined

DB configuration name:

webaccess_highlight_addresscode_underline

• italic

DB configuration name:

webaccess_highlight_addresscode_italic

Enable local client process execution

DB configuration name:

webaccess_use_streamingSmoke

OS4X Webaccess offers a plugin for local file execution ("local CAD system integration"). If this configuration option is enabled, and if the corresponding platform dependant configuration is set up correctly, the user gets a possibility to process files before upload.

The platform dependant script configurations are:

• Windows:
  • Environment listing script URL: streamingSmoke_list_url_Windows
  • DLName listing script URL: streamingSmoke_dlname_url_Windows
  • Export script URL: streamingSmoke_exec_url_Windows
• Mac OS X:
  • Environment listing script URL: streamingSmoke_list_url_MacOSX
  • DLName listing script URL: streamingSmoke_dlname_url_MacOSX
  • Export script URL: streamingSmoke_exec_url_MacOSX
• Linux:
  • Environment listing script URL: streamingSmoke_list_url_Linux
  • DLName listing script URL: streamingSmoke_dlname_url_Linux
  • Export script URL: streamingSmoke_exec_url_Linux
• Other:
  • Environment listing script URL: streamingSmoke_list_url_unsupportedPlatform
  • DLName listing script URL: streamingSmoke_dlname_url_unsupportedPlatform
  • Export script URL: streamingSmoke_exec_url_unsupportedPlatform