webAPX: Help

via a browser using the intranet or an internet connection. Furthermore webAPX offers many statistics presented in form of graphs and the option to generate and display monthly forecasts.

Each user views only his/her authorized production as if he/she was working under APX/PCC.

One of the main goals of webAPX is to distribute the production information to every person involved in the DP production and development without having to install legacy software on his/her workstation.
The DP managers can get at a glance the status of the production and many statistics presented through graphs.
Users accessing the production with webAPX can also be end-users interested in the status of their jobs and applications in production.

webAPX uses the standard authorization of APX to select for each user or group of users the production that can be viewed and eventually modified.

webAPX can therefore be the focus point to access all production information.

webAPX on the server requires the installation of a web-server. Currently Apache and IIS are supported. PHP support on the web-server is mandatory. webAPX can be installed on the APX-Control server or on any server in the network. webAPX can share the web-server with other web-applications. webAPX accesses the Production Database APXDB via the ODBC software

webAPX has an interface to the standard news feeders based on RSS. webAPX has a feed to populate the status of the RCS’s and another to populate the status of the production. The information selected for each feed are user-defined and can be updated at any time. The delay to refresh the RSS-feed is user-defined and the accuracy of this refresh depends on the aggregate, news reader, used.

Functions

· The user authorization is checked against the Production Database when connecting to webAPX.

· webAPX allows to display the following information:

- Status of APX-Control, the production control program,

- Status of the Remote Control Services (RCS’s) and the machines they are running on with selection on active and/or inactive one,

- Status of the Production presenting the tasks and the application’s details
. with selection on the task-names, status and RCS’s
. with zoom on the tasks profiles and the executions graph,
. with the possibility, if allowed by the system administrator, to send commands to APX,
. with display of the execution spools,
. with graphs of the run-time historic information for each job,

- List of all events awaited in production with the option to expand an event-entry to display the tasks awaiting an event. Additionally an event can be manually raised if the webAPX-user has the required authorizations.

- List of all resources defined for the production with the option to expand a resource-entry to display the tasks using or awaiting a resource.

- Authorized profiles from the Production database, the presented tasks can be loaded into production,

- Monthly forecast with zoom on the profiles and the execution’s graph,

- APX production protocol with selection on user and messages,

- Production graphs containing the statistics about tasks, RCS and operating systems,

- RSS feed populating the status of the production and the RCS’s
. with selection on the task-names or status,
. with selection on RCS’s names and status,

- Site specific pages: with webAPX the site gets an entry point to present every authorized user the site specific information about the production. The content and the presentation of these pages are customized by each site and are not maintained by UNISOFTWARE.

· All web pages presented by webAPX share the following features:

- Selection on multiple fields content and criteria,

- Sort of the displayed data by a simple click on the column header; ascending or descending can be selected,

- User defined maximum number of objects displayed on each web page,

- Automatic redisplay of the web pages based on a user defined delay.

· User's preferences are generally stored by the ‘cookies’ in the browser. The cookies contain the login information and the current selections of the user.
The cookies are locally stored and no information from webAPX are sent to external sites.
By default webAPX encrypts the cookies.
The support of cookies can be globally deactivated if the site security policies restrict their usage.
If the site policy allows cookies, each user can decide if he/she allows or not the storage of cookies in his/her browser. The time to live of the cookies is set at the site level and all webAPX cookies of a user can be removed with a simple command as described in the FAQ.

· The length of the fields containing descriptions of the RCS’s, Profiles and the tasks in production as well as the length of the messages from the production protocol presented in the different pages can be customized by each site. With smaller field lengths the web pages will be easier to read. Additionally the full descriptions and messages contents are presented in tool tips attached to these fields. The tool tips are automatically displayed when the cursor stays riefly over a description or a message.

· webAPX can be widely customized via its System Configuration File ‘.../webAPX/system/system.xml’ defining all the options and the default behaviour of the product.
Each site can customize this file in order to apply its own parameters, own behaviour and own security policies.
The content of the System Configuration File is fully documented and can be edited with any text editor. The site customizations will not be overwritten during an upgrade to a new version of the product.

· The look and feel of the webAPX pages can be widely customized due to the utilisation of standard Cascading Style Sheets (CSS).
webAPX proposes 3 levels of style sheets listed below in there increasing priority order. Only the parameters to overwrite should be given at each level without having to re-input the entire style sheet:

- ‘.../webAPX/css/webapxScreen.css’
default CSS from webAPX maintained by UNISOFTWARE, this CSS will be updated with new versions of the product therefore this style sheet should be left unchanged.

- ‘.../webAPX/css/siteScreen.css’
CSS valid for all users of the site, this is the site specific CSS.

- ‘.../webAPX/css/userScreen_sample.css’
CSS valid only for the user i.e. ‘sample’; this is a user specific style sheet.

The number of user style sheets is unlimited. The site and user style sheets will never be automatically updated during an upgrade to a new version of the product.
webAPX offers the same structure of style sheet to print web pages.

· webAPX has Multilanguage support. The default language is stored in the System Configuration File and each user can choose his/her working language during the login procedure.
Any new language can be added after translation of the texts.

· Users under webAPX can change their passwords and font sizes.

Requirements and working environment

· webAPX is currently certified for the database servers: MS-SQL Server, Oracle and DB2.

· The current version of webAPX is certified for the IIS and PHP version 7.1 servers running under Windows in there respective latest versions.

· The current version of webAPX is certified for the Apache2 2.4 and PHP 7.1 servers running under Windows and Linux in there respective latest versions.

· The current version of webAPX is certified for every version of the Windows servers and workstations and all Linux distributions. The 32bits and 64 bits operating systems are supported.

· The current version of webAPX is certified for browser supporting the CSS3 style sheets:
- Microsoft Internet Explorer version 11 and upper,
- Firefox browser version 68 and upper.
Other browsers should be able to display the generated web pages, but webAPX was not tested with them and we will offer no support for the not certified browsers.

Table of webAPX compatibility:

Server / Database	SQL Server	Oracle	DB2
Windows 32 bits (1)	Yes	Yes	Yes
Windows 64 bits	Yes	Yes	Yes
Linux 32 bits (1)	Yes	Yes	Yes
Linux 64 bits	Yes	Yes	Yes
Other UNIXes (2)	Yes	Yes	Yes

Notes:
(1) WebAPX is not tested anymore on those systems but we see no reason the product would not work properly.
(2) WebAPX was not tested on those systems but we see no reason the product would not work properly.