System Architecture Overview

Transcription

Version 1.1.1
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.
Table of Contents
Chapter 1 - Welcome
..............................................................................................................5
1.1 Who should
......................................................................................................................
read this document
6
Chapter 2 - Architecture
..............................................................................................................8
2.1 ISOSYSTEM
......................................................................................................................
Architecture
9
2.2 Network
......................................................................................................................
Architecture
18
2.3 Security
......................................................................................................................
Architecture
19
2.4 Database
......................................................................................................................
Architecture
21
Chapter 3 - Language
..............................................................................................................25
Development
Chapter 4 - Requirements
..............................................................................................................27
4.1 Compatibility
......................................................................................................................
Matrix
28
4.2 Hardware
......................................................................................................................
Requirements
37
4.3 Network
......................................................................................................................
Requirements
38
Chapter 5 - Licensing
..............................................................................................................40
Model
Chapter 6 - Backup
..............................................................................................................42
Chapter 7 - Glossary
..............................................................................................................44
SoftExpert - Software for Excellence
Welcome
Chapter
I
Welcome
1
5
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
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.
Architecture
Chapter
II
8
2
Architecture
ISOSYSTEM Architecture
Network Architecture
Security Architecture
Database Architecture
Architecture
2.1
9
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
2.1.1
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:
Used to open documents, attachments, project and other
executable file, as well as to save documents used in the
ISOSYSTEM Document.
Preview/Associate
Electronic Files:
Used in module ISOSYSTEM Document. This component is used
to associate electronic files in the documents and revisions.
Viewers:
View files CAD, pdf and images directly within browser without
having to install any executable files.
Scan:
Scan documents through scanners.
Jasper Reports:
View reports.
Gantt Project:
Open and edit Gantt structure.
Project Executor:
Execute Project.
Digital Certificate:
Authenticates user in ISOSYSTEM using digital certificate.
Printing Projects:
Used to generate a resizable image of the structure of a project.
Capture Manager
Component:
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.
Architecture
2.1.2
11
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 4.3.11 or 4.4.6 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
SEServices
The "SEServices" is a service package developed in JAVA. Services description are listed
below:
Jasper
Reports:
Reports generator.
Gantt Project:
Edits Gantt structure.
Project
Export:
Converts (export) projects in the ISOSYSTEM project to Microsoft
Project format.
Project
Executor:
Executes Project.
Scan:
Scans documents through scanners.
WorkFlow
Engine:
Starts and executes Process in the ISOSYSTEM WorkFlow.
Scheduler
Used to execute periodic activities automatically, such as import data,
execute OCR, index lots, disconnect user, and send tasks by mail.
PDF
Converter
Converts documents to PDF format.
Digital
Certificate:
Used to validate the digital certificate.
MailOBServer
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:
C:\inetpub\ISOSYSTEMWeb
PHP Files:
C:\Intepub\ISOSYSTEMWeb\wwwroot
PHP Includes:
C:\Intepub\ISOSYSTEMWeb\includes
PHP Executable
Files:
C:\Intepub\ISOSYSTEMWeb\php
Uninstall
Information:
C:\Intepub\ISOSYSTEMWeb\unins000.exe
LOG Files:
C:\Intepub\ISOSYSTEMWeb\wwwroot\log
Configuration File: C:\Intepub\ISOSYSTEMWeb\isosystem.ini
SEServices
Configuration
Services:
C:\Intepub\ISOSYSTEMWeb\seservice.ini
Architecture
13
SEService
Installation
Directory:
C:\Intepub\ISOSYSTEMWeb\wwwroot\generic\app\seservice
LOG Files
SEService:
C:\Intepub\ISOSYSTEMWeb\wwwroot\generic\app\seservice\log
PHP Configuration
C:\Intepub\ISOSYSTEMWeb\php\php.ini
File:
Install Directory of
Document module C:\inetpub\ISOSYSTEMWeb\Document
version 5:
PHP Executable
Files of Document C:\inetpub\ISOSYSTEMWeb\Document\php
module version 5:
Configuration File
of Document
C:\inetpub\ISOSYSTEMWeb\Document\php\isodoc.ini
module version 5:
PHP Configuration
File of Document C:\inetpub\ISOSYSTEMWeb\Document\php\php.ini
module version 5:
Installation
Directory of
Action module:
C:\inetpub\ISOSYSTEMWeb\action
PHP Executable
Files of Action
module:
C:\inetpub\ISOSYSTEMWeb\action\php
Configuration File
C:\inetpub\ISOSYSTEMWeb\action\php\isoaction.ini
of Action module:
PHP Configuration
File of Action
C:\inetpub\ISOSYSTEMWeb\action\php\php.ini
module:
"C:\inetpub\ISOSYSTEMWeb" is defined in the setup.
· Linux:
Installation
Directory:
/usr/local/isosystem/www
PHP Files:
/usr/local/isosystem/www/wwwroot
PHP Includes:
/usr/local/isosystem/www/includes
PHP Executable
Files:
/usr/local/isosystem/apps/php
LOG Files:
/usr/local/isosystem/www/wwwroot/log
14
Configuration File: /usr/local/isosystem/www/isosystem.ini
SEServices
Configuration:
/usr/local/isosystem/www/seservice.ini
SEService
Installation
Directory
/usr/local/isosystem/www/wwwroot/generic/app/seservice
LOG Files
SEService:
/usr/local/isosystem/www/wwwroot/generic/app/seservice/log
PHP Configuration
/usr/local/isosystem/apps/Zend/etc/php.ini
File:
Install Directory of
Document module /usr/local/isosystem/www/Document
version 5:
Configuration File
of Document
/usr/local/isosystem/www/Document/isodoc.ini
module version 5:
Installation
Directory of
Action module:
/usr/local/isosystem/www/action
Configuration File
/usr/local/isosystem/www/action/isoaction.ini
of Action module:
Apache
Installation
Directory:
/usr/local/isosystem/apps/apache2
Startup Scripts:
/usr/local/isosystem/scripts
"/usr/local/isosystem" is defined in the setup.
Architecture
2.1.3
15
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:
C:\SoftExpert
Scripts to
create/update
database:
C:\SoftExpert\ISOSystem\Server\DBWizard
Application
C:\SoftExpert\ISOSystem\Server\SEServer.exe (start as service
Server
ISOSystem - Server”)
Executable Files:
"C:\SoftExpert" is defined in the setup.
16
2.1.4
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).
Architecture
2.1.5
17
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
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.
Architecture
2.3
19
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.
· E-mail 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
· 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.
Architecture
2.4
21
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
8.00.194 is needed.
Max documents size stored in SQL Server is 30Mb. ISOSYSTEM can be
configured to be stored in controlled directory.
22
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.
Architecture
2.4.1
23
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.
Language Development
Chapter
III
3
The Development Platform includes a combination of three languages:
· PHP;
· Delphi;
· Java;
25
Requirements
Chapter
IV
Requirements
4
Requirements
Compatibility Matrix
Hardware Requirements
Network Requirements
27
28
4.1
Requirements
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
Requirements
Client
BI
Calibration
Document
Document Capture
EHS
FMEA
Inspection
Maintenance
MSA
PDF Converter
Performance
Portfolio
Process Map
Product
Project
Risk
SPC
Training
Waste
WorkFlow
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
△
√
√
√
△
√
√
△
√
√
√
√
√
△
△
△
△
△
△
△
1.54 1.62
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
6
7
8
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
√ Approved - Requirement tested and approved to run ISOSYSTEM
properly.
△ In testing - Requirement in the process of validation, please contact
SoftExpert or our partners.
Firefox
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
Microsoft
Office
Client DBMS
Open Acrobat
Office Reader
2007
Audit
2008
Asset
VIsta
APQP-PPAP
2003
Action
Administration
XP
ISOSYSTEM Modules
Internet
Explorer
JRE
Linux
Office Applications3
Browser
2003
Windows
Java
2000
Operating System1
2000
4.1.1
2.x
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√

























√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
● Required - Requirement is necessary to run
ISOSYSTEM properly.
⊗ Unauthorized - Requirement is not compatible.
 Unnecessary - Requirement unused or not required.
30
Requirements
Comments:
1 – Approved to 32-bit operating systems only, for 64 bits contact SoftExpert or our partners.
2 – Requires versions 1.6.03 or lower.
3 – Used to view / edit documents and view attachments.
4 – Version 1.5.15 is not compatible.
Return
31
Requirements
Web Server
Waste
WorkFlow
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√ Approved - Requirement tested and approved to run ISOSYSTEM properly.
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
7
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
7
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
10
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√














●3










E-mail
SMTP IMAP
5.x
SPC
Training
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
PHP4
4.4.6
Risk
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
2.4
Extension
4.3.11
Project
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
7
2
JDK
PDF
Open
Office
1.6
Product
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
6
1.6
Portfolio
Process Map
5
JRE
Apache
1.5
Performance
IBM AIX
MSA
PDF Converter
HP UX
Inspection
Maintenance
Solaris
EHS
FMEA
Debian
Document
Document Capture
Suse
BI
Calibration
Fedora
Audit
RedHat
Asset
1
IIS
2008
APQP-PPAP
Unix
2003
Action
Administration
5
2000
ISOSYSTEM Modules
Linux
2.2.x
Windows
Java
10
WebServer
1.5
6
Operating System
2.x
4.1.2
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
Lotus
Notes8 Application
Server9
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√





●


●
●


●






●





● Required - Requirement is necessary to run ISOSYSTEM properly.
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 1.1.4-4
• Libpng 1.2.2-6
• Libjpeg 6b-21
• Freetype 2 2.1.2-7
• Gd2 2.0.48
• Mhash 0.9.1
• Mcrypt 2.6.x
• Iconv 1.9
• Libxml2 2.6.27
• 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 1.6.03 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.
10 - Version 1.5.15 is not compatible.
DBMS client must be installed and configured in Webserver.
Return
33
Requirements
4.1.3
Application Server
Operating System
Windows
Linux
ISOSYSTEM Modules
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
2000
√
√
√
√
√
√
√
2003
√
√
√
√
√
√
√
2008
△
△
△
△
△
△
△
⊗
⊗
⊗
⊗
⊗
⊗
⊗
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
⊗
⊗
⊗
⊗
⊗
⊗
⊗
⊗
⊗
⊗
⊗
⊗
⊗
⊗
⊗
⊗
⊗
⊗
Java
JRE
Unix
⊗
⊗
⊗
⊗
⊗
⊗
⊗
1.53







1.62







⊗
⊗
⊗
⊗
⊗
⊗
⊗
⊗
⊗
⊗
⊗
⊗
⊗
⊗
⊗
⊗
⊗
⊗

●1










●1






●1










●1





√ Approved - Requirement tested and approved to run ISOSYSTEM
properly.
Comments:
1 – Required if WebServer Operating System is Linux only.
2 – Requires versions 1.6.03 or lower.
3 – Version 1.5.15 is not compatible.
DBMS client must be installed and configured in Application Server.
Return
Requirements
4.1.4
34
Database Server
ISOSYSTEM Modules
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
8.1
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
ORACLE
9i
10g
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
11g
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
DBMS
SQL Server1
2000 2005 2008
√
√
△
√
√
△
√
√
△
√
√
△
√
√
△
√
√
△
√
√
△
√
√
△
√
√
△
√
√
△
√
√
△
√
√
△
√
√
△
√
√
△
√
√
△
√
√
△
√
√
△
√
√
△
√
√
△
√
√
△
√
√
△
√
√
△
√
√
△
√
√
△
√
√
△
Firebird
1.5
2.0
√
⊗
√
⊗
√
⊗
√
⊗
√
⊗
√
⊗
√
⊗
√
⊗
√
⊗
√
⊗
√
⊗
√
⊗
√
⊗
√
⊗
√
⊗
√
⊗
√
⊗
√
⊗
√
⊗
√
⊗
√
⊗
√
⊗
√
⊗
√
⊗
√
⊗
Informix
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
△
√ Approved - Requirement tested and approved to run ISOSYSTEM properly.
△ In testing - Requirement in the process of validation, please contact SoftExpert or our
partners.
⊗ 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
Requirements
Product
Project
Risk
SPC
Training
Waste
WorkFlow













































●







●








●



●





















●
































































































































ISOSYSTEM Server1


●







●


●




WorkFlow
Process Map
Portfolio
Maintenance
Inspection
Document Capture
BI















Waste
Process Map

























Training
Portfolio














●
●


●



●
●

●




●


●



SPC
Performance


























Risk
PDF Converter


























Project
MSA


























Product
Maintenance
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
Performance
Inspection


























PDF Converter
FMEA
●





●



















Object
EHS


























MSA
Document Capture


























Generic
Document


























FMEA
Calibration


●






●
















EHS
BI


























Document
Audit
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●


●
Calibration
Asset


Audit
APQP-PPAP
























Asset
●
Action
Administration
APQP-PPAP
ISOSYSTEM Modules
Administration
Module Requirements
Action
4.1.5





●



●


●












√ Approved - Requirement tested and approved to run ISOSYSTEM properly. ● Required - Requirement is necessary to run ISOSYSTEM properly.
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
Requirements
4.2
37
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
Requirements
4.3
Network Requirements
Web Server
Use the Link with Document
Module
Use the Link with other modules
Per user
30 kbps
20 kbps
Application Server
Use the Link
Per user
12 kbps
Licensing Model
Chapter
V
40
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.
Backup
Chapter
VI
42
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) 2
1 - 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 1.3.1 or higher contains the procedure for backup and
restore with DBMS Firebird, for other DBMS consult the supplier of DBMS.
Glossary
Chapter
VII
44
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).
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
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.

System Architecture Overview

Transcription

Similar documents

File Processing Using PHP on IBM i

Media Pack - The Directory Group

Hospital Trustees Celebrate Quality Initiatives

PENGANTAR MANAJEMEN BASIS DATA

The California Society of Municipal Finance Officers (CSMFO

Memorandum - Department of Education, Region IV | Calabarzon

Deepak Chopra

Setup and Status of .fo today – Isak Jakobsen, .fo

Spring, 2014 - Vol.13, No.1 2014 NAPAT NATIONAL AWARD

NFL Game Pass Walkthrough

2014 Boca Raton Concours D`elegance Presented By mercedes-benz

Finding User Navigation Patterns to Improve Website Usability

eTrust Directory Administrator Guide

Active Directory Domain Services Replication