System Architecture Overview. Version 1.1.1

Transcription

1 System Architecture Overview Version 1.1.1

2 The information in this document is subject to modification without any previous notice. Data used in the examples are fictitious. It is prohibited to reproduce any part of this guide in any shape or form by way of media: electronic or printed, for any purpose, without prior explicit written permission from SoftExpert Quality Software. SOFTEXPERT and ISOSYSTEM are registered trademarks of SoftExpert Quality Software. Other product names mentioned in this guide are registered trademarks of those respective companies.

3 Table of Contents Chapter 1 - Welcome Who should... read this document 6 Chapter 2 - Architecture ISOSYSTEM... Architecture Network... Architecture Security... Architecture Database... Architecture 21 Chapter 3 - Language...25 Development Chapter 4 - Requirements Compatibility... Matrix Hardware... Requirements Network... Requirements 38 Chapter 5 - Licensing...40 Model Chapter 6 - Backup...42 Chapter 7 - Glossary...44

4 Welcome Chapter I

5 Welcome 5 1 Welcome This is the System Architecture Overview, designed to be used by anyone who wants a general understanding of the ISOSYSTEM operation and resources.

6 6 System Architecture Overview 1.1 Who should read this document System Architecture Overview contains information that is helpful to: Anyone who wants a general understanding of the ISOSYSTEM architecture, services, component layout distribution, used technologies, requirements and licensing. IT personnel responsible for the rollout of ISOYSTEM, who must understand how ISOSYSTEM operates to define the best way to integrate the ISOSYSTEM with infrastructure and software policies. IT personnel responsible for the support of ISOYSTEM, who must understand how ISOSYSTEM operates to identify possible problems in the system. Purpose This document details ISOSYSTEM operation and resources, through architecture, component layout distribution, used technologies, requirements and licensing. Use this guide to determine which third-party softwares are compatible and the infrastructure necessary to run ISOSYSTEM properly. CAUTION Even though SoftExpert provides support for newly released versions of third-party service packs and patches, SoftExpert has no control over the content of these software updates and therefore cannot unequivocally guarantee compatibility with our product set. In all cases, you should check the vendor's product specifications for information about the products supported.

7 Architecture Chapter II

8 8 System Architecture Overview 2 Architecture ISOSYSTEM Architecture Network Architecture Security Architecture Database Architecture

9 Architecture ISOSYSTEM Architecture ISOSYSTEM is based on three tier architecture: User; Logic Functional Process ( business ); Storage and data access; Layers are developed and maintained independently, allowing to operate the complete solution in one or multiple servers, facilitating the load balance. See the diagram: Client Web Server Application Server Database Server File Server

10 10 System Architecture Overview Client ISOSYSTEM is accessed in the browser and the workstation must meet the requirements. It s not necessary to install any ISOSYSTEM component in workstation. Java Components ISOSYSTEM uses several components developed in JAVA. The main components are listed below: Upload/Download: Preview/Associate Electronic Files: Viewers: Scan: Jasper Reports: Gantt Project: Project Executor: Digital Certificate: Printing Projects: Capture Manager Component: Used to open documents, attachments, project and other executable file, as well as to save documents used in the ISOSYSTEM Document. Used in module ISOSYSTEM Document. This component is used to associate electronic files in the documents and revisions. View files CAD, pdf and images directly within browser without having to install any executable files. Scan documents through scanners. View reports. Open and edit Gantt structure. Execute Project. Authenticates user in ISOSYSTEM using digital certificate. Used to generate a resizable image of the structure of a project. Used to create lot where the user will capture images (scanner or directory), configure, and verify OCR. Executable Files ISOSYSTEM downloads compressed files on the workstation to execute components and modules WEB-DB, for example, the module ISOSYSTEM BI. These files are unpacked at run time and remain in the temporary directory of the user, with no need of new download in every access to ISOSYSTEM, avoiding unnecessary network traffic. WEB-DB Modules: Client/Server modules, accessed in the browser of a workstation without the need of installation in the client.

11 Architecture Web Server ISOSYSTEM is a Web Application accessed through Web Server (Apache or IIS) supported PHP. The service seservices is installed and configured along with Web Application. ISOSYSTEM supports any port configured by web server and also supports secure connections using HTTPS protocol. Apache The Apache Web Server should be used only in Unix environments. Apache must be compiled using --enable-so and must be unique to the ISOSYSTEM. PHP: The PHP version should be or compiled with support for all software requirements. IIS The IIS Web Server (Internet Information Service) is pre configured during setup, just some configuration is necessary for the proper functioning of ISOSYSTEM. PHP: The PHP is installed and configured during ISOSYSTEM setup. Details on the installation and configuration of PHP are: PHP files are installed in ISOSYSTEM directory; The ISAPI DLL must be enabled in Service Extension of IIS (Case IIS version is compatible); Create key in Windows Registry: HKEY_LOCAL_MACHINE\SOFTWARE\ISOSYSTEM\FASTCGI; The PHP run as ISAPI DLL. PHP support in IIS is configured only in virtual directory isosystem, document and action. It is necessary to create new application pool configured in flap Identity as Local System (Case IIS version is compatible);

12 12 System Architecture Overview SEServices The "SEServices" is a service package developed in JAVA. Services description are listed below: Jasper Reports: Gantt Project: Project Export: Project Executor: Scan: WorkFlow Engine: Scheduler PDF Converter Digital Certificate: MailOBServer Reports generator. Edits Gantt structure. Converts (export) projects in the ISOSYSTEM project to Microsoft Project format. Executes Project. Scans documents through scanners. Starts and executes Process in the ISOSYSTEM WorkFlow. Used to execute periodic activities automatically, such as import data, execute OCR, index lots, disconnect user, and send tasks by mail. Converts documents to PDF format. Used to validate the digital certificate. Monitors a mail account, if the mail meets the predefined rules, returns the mail to the sender with project data. Directories and Files Structure Windows: Installation Directory: PHP Files: PHP Includes: PHP Executable Files: Uninstall Information: LOG Files: C:\inetpub\ISOSYSTEMWeb C:\Intepub\ISOSYSTEMWeb\wwwroot C:\Intepub\ISOSYSTEMWeb\includes C:\Intepub\ISOSYSTEMWeb\php C:\Intepub\ISOSYSTEMWeb\unins000.exe C:\Intepub\ISOSYSTEMWeb\wwwroot\log Configuration File: C:\Intepub\ISOSYSTEMWeb\isosystem.ini SEServices Configuration Services: C:\Intepub\ISOSYSTEMWeb\seservice.ini

13 Architecture 13 SEService Installation Directory: LOG Files SEService: PHP Configuration File: Install Directory of Document module version 5: PHP Executable Files of Document module version 5: Configuration File of Document module version 5: PHP Configuration File of Document module version 5: Installation Directory of Action module: PHP Executable Files of Action module: Configuration File of Action module: PHP Configuration File of Action module: C:\Intepub\ISOSYSTEMWeb\wwwroot\generic\app\seservice C:\Intepub\ISOSYSTEMWeb\wwwroot\generic\app\seservice\log C:\Intepub\ISOSYSTEMWeb\php\php.ini C:\inetpub\ISOSYSTEMWeb\Document C:\inetpub\ISOSYSTEMWeb\Document\php C:\inetpub\ISOSYSTEMWeb\Document\php\isodoc.ini C:\inetpub\ISOSYSTEMWeb\Document\php\php.ini C:\inetpub\ISOSYSTEMWeb\action C:\inetpub\ISOSYSTEMWeb\action\php C:\inetpub\ISOSYSTEMWeb\action\php\isoaction.ini C:\inetpub\ISOSYSTEMWeb\action\php\php.ini "C:\inetpub\ISOSYSTEMWeb" is defined in the setup. Linux: Installation Directory: PHP Files: PHP Includes: PHP Executable Files: LOG Files: /usr/local/isosystem/www /usr/local/isosystem/www/wwwroot /usr/local/isosystem/www/includes /usr/local/isosystem/apps/php /usr/local/isosystem/www/wwwroot/log

14 14 System Architecture Overview Configuration File: /usr/local/isosystem/www/isosystem.ini SEServices Configuration: SEService Installation Directory LOG Files SEService: PHP Configuration File: Install Directory of Document module version 5: Configuration File of Document module version 5: Installation Directory of Action module: Configuration File of Action module: Apache Installation Directory: Startup Scripts: /usr/local/isosystem/www/seservice.ini /usr/local/isosystem/www/wwwroot/generic/app/seservice /usr/local/isosystem/www/wwwroot/generic/app/seservice/log /usr/local/isosystem/apps/zend/etc/php.ini /usr/local/isosystem/www/document /usr/local/isosystem/www/document/isodoc.ini /usr/local/isosystem/www/action /usr/local/isosystem/www/action/isoaction.ini /usr/local/isosystem/apps/apache2 /usr/local/isosystem/scripts "/usr/local/isosystem" is defined in the setup.

15 Architecture Application Server ISOSYSTEM Server is a proprietary application, installed as a Windows service, used to connect Client/Server modules with the database. Directories and Files Structure Installation Directory: Scripts to create/update database: Application Server Executable Files: C:\SoftExpert C:\SoftExpert\ISOSystem\Server\DBWizard C:\SoftExpert\ISOSystem\Server\SEServer.exe (start as service ISOSystem - Server ) "C:\SoftExpert" is defined in the setup.

16 16 System Architecture Overview Database Server ISOSYSTEM is optimized to use several DBMS (Database Manager System) commercials or open source. Customer chooses DBMS, and it must meet the software requirements. The module ISOSYSTEM Document stores documents in database or in Controlled Directory (File Server).

17 Architecture File Server It is used to store documents in module ISOSYSTEM Documents in Controlled Directory, which can be a local directory or a sharing network. If database is used to store documents, File Server is not necessary.

18 18 System Architecture Overview 2.2 Network Architecture Ports listed above are the patterns of each service, and may have variations according to configuration. The firewall should be configured so that LAN and WAN Workstations access the servers Web Server and Application Server in the ports of service below: Ports Used for Services: 80 : HTTP Web Server 433 : HTTPS 5009 : SEServices Application Server 9000 : ISOSYSTEM Server Mails are sent from Web Server only. The Workstation does not need to have access to the mail server. Only the Client/ Server modules send mail from workstation, and in this case, it will be necessary that the workstations have access to the mail server.

19 Architecture Security Architecture Login Login User and Password: The users passwords are stored in the database and encrypted using ISOSYSTEM own algorithm. In the authentication process, the application encrypts the password that was informed in the login form and compares it with the encrypted password stored in the database. User and Password: If the authentication password to send mail is enabled, the password is stored in database, using ISOSYSTEM encryption algorithm. Active Directory Integration (Single Sign-On): The Active Directory Integration consists of importing users from LDAP, also allowing to import data such as departments and positions of the organizational structure of the Active Directory. The authentication with Active Directory is performed by IIS through Integrated Windows Authentication. ISOSYSTEM compares the user logged in windows with the users table on database allowing or denying access to ISOSYSTEM. The option integrated authentication can be disabled on the login screen. You may inform your login data manually (this option can also be disabled in administration module). This option allows easy integration with intranet portals.

20 20 System Architecture Overview Digital Certificate: When the option "Authentication using SmartCard Single Sign-On" is enabled in the Administration module, user informs login and password during the first access in ISOSYSTEM, and the digital certificate is associated with the user. In the next accesses, user needs only the digital certificate to sign in. Access Control The access control to each feature is managed through access rights associated with each menu item. Access is configured through access group with users groups association. Some resources can be blocked by the application (project cost, for example). This function enables managers to select those users who will have the right to access specific information. Unauthorized Access Some security policies can be configured in Administration module to increase security against unauthorized Access: Password Expiration, requiring password to be changed by the user. Block user by number of attempts. Sending mail to the manager when a user is blocked by exceeding the number of attempts. Database Connection Configuration The settings for connecting to database are stored in encrypted configuration files, using ISOSYSTEM encryption algorithm.

21 Architecture Database Architecture The creation of objects in the database is accomplished through SoftExpert proprietary software (DBWizard). The DBWizard connects with the DBMS through ADO connection, and creates script to create/update database according to parameterization. The DBWizard user to connect database needs DBA permissions. The script is displayed before running, and after that, log file is generated with all executed commands. The creation of objects in the database can also run manually through scripts. Oracle With DBMS Oracle, the DBWizard creates user/schema with DBA permissions and the TABLESPACES that will be used by ISOSYSTEM modules. To create / update objects in the database, user needs to have connect and resource permissions. To connect application, user needs to have connect, insert, update, delete and create sequence permissions. Synonyms can be used to increase security. ISOSYSTEM supports default configuration of Oracle, not requiring any specific configuration. This DBMS is recommended for large volume of data and transactions. SQL Server With DBMS SQL Server, it is necessary to create a New Login configured as SQL Server Authentication and default language configured as default or English. User needs to have public and db_owner permissions in the ISOSYSTEM database. This DBMS is recommended for medium volume of data and transactions. The SQL Server shall be configured to login with SQL Server Authentication. With SQL Server 2005, it is necessary to enable TCP/IP connections in the DBMS configuration and in the Web Server, the DLL ntwdblib.dll version is needed. Max documents size stored in SQL Server is 30Mb. ISOSYSTEM can be configured to be stored in controlled directory.

22 22 System Architecture Overview Firebird The Firebird is a powerful DBMS open source, recommended to maintain a good performance, without having to spend with DBMS license. Specific configurations are not necessary. This DBMS is recommended for small volume of data and transactions.

23 Architecture Database Connection ISOSYSTEM Server ISOSYSTEM Server is an intermediate between the DBMS and client application. ISOSYSTEM Server connection with database uses ADO connection. Client/Server modules connection with ISOSYSTEM Server uses socket through ASTA. This connection is encrypted ensuring data security. The ASTA component does not require installation and configuration of DBMS client at Workstations. SEServices In JAVA applications, the connection uses JDBC driver, without the need of installing DBMS driver. Web Modules In the Web modules, the connection with database uses native DBMS driver of each DBMS.

24 Language Development Chapter III

25 Language Development 25 3 Language Development The Development Platform includes a combination of three languages: PHP; Delphi; Java;

26 Requirements Chapter IV

27 Requirements 27 4 Requirements Compatibility Matrix Hardware Requirements Network Requirements

28 28 Requirements 4.1 Compatibility Matrix Click on textbox below to view Compatibility Matrix of Client, WebServer, Application Server and Database Server: Click on image below to view Modules Requirements:

29 29 Requirements Client Operating System 1 Java Browser Office Applications 3 Windows Linux JRE Internet Explorer Firefox Microsoft Office Open Office Acrobat Reader Client DBMS ISOSYSTEM Modules 2000 XP 2003 VIsta Action Administration APQP-PPAP Asset Audit BI Calibration Document Document Capture EHS FMEA Inspection Maintenance MSA PDF Converter Performance Portfolio Process Map Product Project Risk SPC Training Waste WorkFlow x Approved - Requirement tested and approved to run ISOSYSTEM properly. In testing - Requirement in the process of validation, please contact SoftExpert or our partners. Required - Requirement is necessary to run ISOSYSTEM properly. Unauthorized - Requirement is not compatible. Unnecessary - Requirement unused or not required.

30 30 Requirements Comments: 1 Approved to 32-bit operating systems only, for 64 bits contact SoftExpert or our partners. 2 Requires versions or lower. 3 Used to view / edit documents and view attachments. 4 Version is not compatible. Return

31 31 Requirements Web Server ISOSYSTEM Modules Operating System 6 WebServer Java Windows Linux 5 Unix IIS Apache 1 JRE JDK RedHat Fedora Suse Debian Solaris HP UX IBM AIX x 2.2.x PDF Open Office 2.4 Extension PHP x SMTP IMAP Lotus Notes 8 Application Server 9 Action Administration APQP-PPAP Asset Audit BI Calibration Document Document Capture EHS FMEA Inspection Maintenance MSA PDF Converter 3 Performance Portfolio Process Map Product Project Risk SPC Training Waste WorkFlow Approved - Requirement tested and approved to run ISOSYSTEM properly. In testing - Requirement in the process of validation, please contact SoftExpert or our partners. Required - Requirement is necessary to run ISOSYSTEM properly. Unauthorized - Requirement is not compatible. Unnecessary - Requirement unused or not required.

32 32 Requirements Comments: 1 - ISOSYSTEM with Apache WebServer is compatible in Linux only. 2 - Required if WorkFlow module is installed in Linux. If it is installed in Windows, Java JRE can be used. 3 - OpenOffice does not need to be installed in the same server in which ISOSYSTEM is. 4 - The PHP on Windows is installed during ISOSYSTEM setup without the need of user intervention. In Linux, the PHP must be compiled with support to the following libraries: Zlib Libpng Libjpeg 6b-21 Freetype Gd Mhash Mcrypt 2.6.x Iconv 1.9 Libxml Java JDK 1.5 or higher And additional support to the following features: Bcmath Mbstring Dom Ttf GD Native Ttf 5 - The modules are compatible with Linux, though some may require an application server to run specific components. 6 - ISOSYSTEM is compatible with 64bit operating systems in Linux. In Windows 2003, the IIS must be configured to emulate 32-bit, and windows 2008 is in testing. 7 - Requires versions or lower. 8 - Compatible if WebServer Operating System is Windows. 9 - Application Server is compatible with Windows only, if WebServer Operating System is Linux, an additional server with Windows will be necessary for proper operation of these modules Version is not compatible. DBMS client must be installed and configured in Webserver. Return

33 33 Requirements Application Server Operating System Windows Linux Unix ISOSYSTEM Modules Action Administration APQP-PPAP Asset Audit BI Calibration Document Document Capture 1 1 EHS FMEA Inspection Maintenance MSA PDF Converter Performance Portfolio Process Map Product Project 1 1 Risk SPC Training Waste WorkFlow Approved - Requirement tested and approved to run ISOSYSTEM properly. In testing - Requirement in the process of validation, please contact SoftExpert or our partners. Required - Requirement is necessary to run ISOSYSTEM properly. Unauthorized - Requirement is not compatible. Unnecessary - Requirement unused or not required. Comments: 1 Required if WebServer Operating System is Linux only. 2 Requires versions or lower. 3 Version is not compatible. Java JRE DBMS client must be installed and configured in Application Server. Return

34 Requirements Database Server DBMS ORACLE SQL Server 1 Firebird Informix ISOSYSTEM Modules 8.1 9i 10g 11g Action Administration APQP-PPAP Asset Audit BI Calibration Document Document Capture EHS FMEA Inspection Maintenance MSA PDF Converter Performance Portfolio Process Map Product Project Risk SPC Training Waste WorkFlow Approved - Requirement tested and approved to run ISOSYSTEM properly. In testing - Requirement in the process of validation, please contact SoftExpert or our partners. Required - Requirement is necessary to run ISOSYSTEM properly. Unauthorized - Requirement is not compatible Unnecessary - Requirement unused or not required Comments: 1 Max documents size store in SQL Server is 30Mb. Documents can be configured to be stored in controlled directory The Operating System of Database Server does not affect the operation of ISOSYSTEM. Return

35 35 Requirements Module Requirements ISOSYSTEM Modules Action Administration APQP-PPAP Asset Audit BI Calibration Document Document Capture EHS FMEA Generic Action Administration APQP-PPAP Asset Audit BI Calibration Document Document Capture EHS FMEA Inspection Maintenance MSA PDF Converter Performance Portfolio Process Map Product Project Risk SPC Training Waste WorkFlow Inspection Maintenance MSA Object PDF Converter Performance Portfolio Process Map Product Project Risk SPC Training Waste WorkFlow ISOSYSTEM Server 1 Approved - Requirement tested and approved to run ISOSYSTEM properly. In testing - Requirement in the process of validation, please contact SoftExpert or our partners. Required - Requirement is necessary to run ISOSYSTEM properly. Unauthorized - Requirement is not compatible. Unnecessary - Requirement unused or not required.

36 36 Requirements Comments: 1 - ISOSYSTEM Server is installed and configured in Application Server. WebServer and Application Server can be the same server if their operating system is Windows. Return

37 Requirements Hardware Requirements Web Server Processor RAM Memory Disk Space Up to 10 users 2.0Ghz 1GB 1 Gb From 10 to 25 users 3.0Ghz 2GB 1 Gb From 25 to 50 users Xeon 3.0Ghz 3GB 1 Gb Application Server Processor RAM Memory Disk Space Up to 50 users 1.8Ghz 1GB 1 Gb Workstation Processor RAM Memory Disk Space 1.8Ghz 1GB 200 Mb Considering DBMS is installed on independent server. If the number of concurrent users higher than 50, please contact SoftExpert or our partners.

38 38 Requirements 4.3 Network Requirements Web Server Use the Link with Document Module Per user 30 kbps 20 kbps Use the Link with other modules Application Server Per user Use the Link 12 kbps

39 Licensing Model Chapter V

40 40 System Architecture Overview 5 Licensing Model ISOSYSTEM is licensed per user. License may be: Simultaneous: The number of licenses applies to the number of concurrent users connected at ISOSYSTEM per profile (Manager, Staff and View). It does not depend on the amount of registered users. Nominative: The number of licenses applies to active users registered in the ISOSYSTEM per profile (Manager, Staff e View). In both cases, license may be: Individual: The license is valid for each module individually. Shared / Packages: The license is valid for any module that is part of the package. All types of licenses can be permanent or monthly. Below there is a description of user profiles: ISOSYSTEM - Manager: All menus of the system are available, according to the established rights of access for each user. ISOSYSTEM - Staff: It has intermediate access to certain stages of the system, according to the established rights of access for each user. ISOSYSTEM - View: Permission only to consult, in accordance with the established rights of access for each user.

41 Backup Chapter VI

42 42 System Architecture Overview 6 Backup ISOSYSTEM stores data in database. Documents can be configured to be stored in database or controlled directory. The FTS Service stores indexing data in directory. Regular backup is required: Database Controlled Directory 1 Indexing Data Directory (FTS data) If ISOSYSTEM is configured to store documents in Controlled Directory. 2 - If the FTS service is installed and configured. The installation directories do not need to be included in regular backup. It is only necessary to perform backup before and after carrying out ISOSYSTEM upgrades. The Installation Guide or higher contains the procedure for backup and restore with DBMS Firebird, for other DBMS consult the supplier of DBMS.

43 Glossary Chapter VII

44 44 System Architecture Overview 7 Glossary A ADO (ActiveX Data Objects): ADO is a programming interface to access data in a database. ASTA: The component ASTA allows communication between 2 processes through socket in a TCP / IP network. Active Directory: Active Directory (AD) is an implementation of LDAP directory services by Microsoft for use primarily in Windows environments. Its main purpose is to provide central authentication and authorization services for Windows-based computers. D DBMS (Database Management System): A DBMS is a complex set of software programs that controls the organization, storage, management, and retrieval of data in a database. DBMS Driver: A program installed on a workstation or server to allow programs on that system to interact with a DBMS. DBWizard: DBWizard is a proprietary software of SoftExpert, using to create/update database. Directory Service: A directory is similar to a database, but tends to contain more descriptive information, based on attribute, and it is organized in the shape of a tree. F Firewall: A firewall is a set of related programs, located at a network that protects the resources of a private network from users from other networks. FTS: This is an application developed in Java by SoftExpert for contents indexing of documents. H HTTP (Hypertext Transfer Protocol): It is a communication protocol to transfer information on intranets and the World Wide Web. HTTPS: A secure version of HTTP (using SSL).

45 Glossary 45 I IMAP (Internet Message Access Protocol): It is an application layer Internet protocol that allows a local client to access mail on a remote server. ISAPI (Internet Server Application Program Interface): They are applications, similar to the CGI, which run the server side and the integrated Web Server. ISOSYSTEM Server: It is an application developed by SoftExpert, and it is used as an intermediate between the DBMS and client application. J JDBC (Java Database Connectivity): JDBC is a set of classes and interfaces (API) written in Java which is the sending of SQL statements for any relational database from Java environment. L LAN (Local Area Network): It is a network of computers that does not extend beyond the physical limits of any building. Normally used in companies to interconnect their local computers. LDAP (Lightweight Directory Access Protocol): LDAP is a protocol (run on TCP / IP) client-server, used to access a directory service. O OCR (Optical Character Recognition): Technology used to identify characters in an image. S SEServices: It is a package of applications developed in Java by Softexpert. Single Sign-On: It represents the possibility for a user to access all the applications that have access through a single login and password. SmartCard: A plastic card which contains a computer chip. The card is used for performing operations which require the data that is stored on the chip. SMTP (Simple Mail Transport Protocol): Protocol for transmission of mail used in TCP/IP networks. Socket: The socket opens the network connection for a program, allowing data to be read and written over the network.

46 46 System Architecture Overview T TCP/IP (Transmission Control Protocol/Internet Protocol): It is a set of protocols for communication between network computers. W WAN (Wide Area Network): It is a network that spans a large geographical area, the most common example is the Internet. WEB-DB Modules: Client Server modules, accessed in the browser of a workstation.