Saudi Railways Company

SAR BPM Project (0319)

AppWorks - Architecture Design

Specifications

The Information Company™

ENTERPRISE INFORMATION MANAGEMENT 1

 Contents
1............................................................................... Introduction about SAR 5

1.1 Glossary of Terms.......................................................................................... 5

2.................................................................................................... Disclaimer 6

3........................................................... Business and Technical Requirements 7

3.1 Business Scope.............................................................................................. 7

3.2 Scalability..................................................................................................... 7

3.3 Preferred Platforms........................................................................................ 7

3.4 Integrations................................................................................................... 8
3.4.1 OpenText Extended ECM...............................................................................8
3.4.2 Oracle EBS integration..................................................................................8
3.4.3 Email Integration..........................................................................................8

3.5 User Base...................................................................................................... 8

3.6 User Demographics........................................................................................ 9

4...................................................................................... Architecture Design 10

4.1 AppWorks platform overview.......................................................................10

4.2 AppWorks Architecture................................................................................11

4.3 Design time architecture...............................................................................11

4.4 Runtime architecture....................................................................................12

4.5 AppWorks runtime components overview......................................................14

4.5.1 Entity modeling :......................................................................................... 14
4.5.2 Business Process /Activity Management:........................................................14
4.5.3 User interfaces:........................................................................................... 15
4.5.4 Integrations – Enterprise information system connectivity :............................15
4.5.5 Document store:.......................................................................................... 15
4.5.6 Scheduling :................................................................................................ 16
4.5.7 Technology Standard compliances:...............................................................17

4.6 AppWorks Security......................................................................................17

4.6.1 Authentication:............................................................................................ 17
4.6.2 Authorization:............................................................................................. 19

5.......................................................................................... High Availability 20

ENTERPRISE INFORMATION MANAGEMENT 2

 5.1 High Availability qualities and requirements...................................................20

5.2 High Availability Architecture......................................................................20

5.3 Load Balancing............................................................................................21

5.4 SSL Encryption........................................................................................... 21

6................................................................................. Backup Considerations 21

6.1 Backup components.....................................................................................21

6.2 Application directories backup......................................................................22

7............................................................................................... Environments 23

7.1 Development environment............................................................................23

7.1.1 Architecture................................................................................................ 23
7.1.2 Machine requirements..................................................................................24
7.1.3 AppWorks Installation Details.......................................................................24
7.1.4 AppWorks Platform access details :..............................................................26

7.2 Test/QA environment...................................................................................27

7.2.1 Architecture................................................................................................ 27
7.2.2 Machine requirements..................................................................................28
7.2.3 AppWorks Installation Details.......................................................................28
7.2.4 AppWorks License Key.................................................................................30
7.2.5 AppWorks Platform access details.................................................................30

7.3 Production environment................................................................................31

7.3.1 Architecture................................................................................................ 31
7.3.2 Machine requirements..................................................................................31
7.3.3 AppWorks Installation Details.......................................................................32
7.3.4 AppWorks License Key.................................................................................34
7.3.5 AppWorks Platform Access details................................................................34

8............................................................................... Software Version Details 35

8.1 Opentext Software Versions..........................................................................35

8.2 Third-Party Software versions.......................................................................35

8.3 Patches....................................................................................................... 35

9................................................................................................... Conclusion 35

10........................................................................... Acceptance of Deliverable 36

About OpenText.............................................................................................. 36

ENTERPRISE INFORMATION MANAGEMENT 3

ENTERPRISE INFORMATION MANAGEMENT 4
Document Change History
Version Date Modified Author Comments
1.0 09/15/2021 Pavan Kumar Initial DRAFT
1.1 09/30/2021 Nageswara Rao Environment update
1.2 10/03/2021 Nageswara Rao Production details and HA update

Document Change History

ENTERPRISE INFORMATION MANAGEMENT 5

 1 Introduction about SAR
Established in 2006, SAR is the owner and operator of the North Train Railway Network in Saudi
Arabia, and now, the new enabler of Railway industry, and carries on the vision to build a
sustainable passenger and cargo transport in the Kingdom. It has been a story of success for the
railway industry. Taking into consideration the networks that have been established in the past
decade, and the enormity of these projects which are amongst the largest infrastructure developments
in the Kingdom. SAR trains currently run through three main networks (North - East - Harman) with
lengths of more than 5,500 km, through which more than 33 million passengers have been
transported.
As part of new & ambitious digitization program, SAR is reengineering and automating most of its
core & support processes. One of these high-priority processes is the Automation of Shipment
Tracking process which is used by the Logistics Team and External Teams (Suppliers, Freight
Forwarded, Brokers).The current challenge is that existing system cannot be exposed to external
teams due to which the Logistics Team has to function manually over emails and calls to identify and
update the correct status of the shipment.

1.1 Glossary of Terms

Term Description
SAR Saidy Railways Company (Customer)
AppWorks Opentext AppWorks
xECM OpenText Extended ECM
OTCS, CS OpenText Content Server
OTDS OpenText Directory Services
OTAC, AC OpenText Archive Center
OTSC, SC OpenText System Center
EIM Enterprise Information Management
HLD High Level Design
TDD Technical Design Document
LMM Low Memory Mode
ENTERPRISE INFORMATION MANAGEMENT 6
 Term Description
AD (Microsoft) Active Directory
EC Enterprise Connect
VM Virtual Machine(s)
HTTPS Hypertext Transfer Protocol (Secure)
TLS Transport Layer Security
IWA Integrated Windows Authentication
SSO Single Sign-on
BWS Business Workspace
CWS Content Web Services
HA High Availability
Glossary of Terms

2 Disclaimer
This is a living document that should be updated regularly as requirements are clarified, added or
changed. Therefore, it is important to monitor early usage to acquire precise usage patterns and to
consequently resize the architecture accordingly.
The information used to produce this estimate is constantly being updated and is subject to change
without notice. Some of the updated information may directly impact this architecture design.
OpenText makes every effort to ensure the accuracy of this information according to the information
available; however, some empirical data is used in various calculations, which is not specific to SAR
environment, and therefore actual results may vary.

ENTERPRISE INFORMATION MANAGEMENT 7

 3 Business and Technical Requirements
The following section summarizes the explicit requirements identified by OpenText and agreed to by
SAR for their Business Process Management

3.1 Business Scope

The deployment of the OpenText solution at SAR responds to an immediate need to implement the
following business processes.

Business Process Ref Document

Fuel Management TBD
Letter of Issuance TBD
Brand & Artwork TBD
Business Planning TBD
Shipment tracking TBD

3.2 Scalability
To facilitate the development and roll-out of the system for the immediate needs, this document set

proposes an architecture that will support the resources required for the deployment of the solution.

OpenText will also outline what the scaled-up architecture for the solution beyond the initial known

goals of the project will look like and will take into consideration the aspects of scaling up from the

initial architecture to a larger solution if needed. However, the primary driver identified for this

deployment is expected to be the load capacity requirements.

ENTERPRISE INFORMATION MANAGEMENT 8

 3.3 Preferred Platforms
This section presents the SAR preferred platforms that are relevant to this implementation. OpenText

design decisions are based on these platforms, any challenges will be called out accordingly.

Server Role OS/Software version

AppWorks Windows 2019
OTDS Windows 2019
Database Microsoft SQL 2019
Load Balancer F5
Virtualization VMware ESX
Client
Windows 10 64-Bit
Environment
Authentication Microsoft AD
System
User Repository Microsoft AD
Preferred Platforms

Any other software components that will be involved in SAR OpenText based system are expected to

be hosted on a supported Microsoft Windows platform.

SAR has expressed their preference to use VMware virtual servers wherever possible..

3.4 Integrations
SAR has indicated that following integrations will be part of the scope.

 Opentext Content Server

 Oracle EBS

 Email integration

3.4.1 OpenText Extended ECM

AppWorks ECM will be used to store all the processed documents from AppWorks . Opentext

extended ECM will be used to connect and store all the documents.

ENTERPRISE INFORMATION MANAGEMENT 9

3.4.2 Oracle EBS integration

SAR uses Oracle EBS as their back end ERP , AppWorks can connect to the functions of Oracle

EBS with required web services . AppWorks exposes the required services to be consumed by Oracle
EBS and Oracle EBS has to expose required web services to consume at AppWorks .

3.4.3 Email Integration

Opentext AppWorks uses the standard Appwork Email connector to send / receive emails to SAR
users .

3.5 User Base

SAR has identified the expected user base and number of active users of the system. SAR is

expecting the AppWorks will be used by about 200 users. The following tables summarize the user

metric information.

Phas Estimated
e Users
Phase 1 200
Phase II TBD
Total 200
Named End Users for the application

Using the following definitions:

Named Users who have access to Open Text AppWorks and

Users that are recognized independently from one another

through credentials, login access.

ENTERPRISE INFORMATION MANAGEMENT 10

 Active Active (or Session) Users that are logged into Open

Users Text Appwroks same time. They don’t have to enter or

exit Open Text Appwroks at the same time, but if there

is a time that those two users are logged in Open Text

AppWorks during the same period, then they are

considered active..
Concurrent Concurrent users (concurrent use) that are requesting

Users Open Text AppWorks to perform an operation at the

same time (during the same split second).

3.6 User Demographics

SAR ’s user-base is primarily in KSA.

ENTERPRISE INFORMATION MANAGEMENT 11

 4 Architecture Design

4.1 AppWorks platform overview

OpenText AppWorks is the ideal solution to build new processes and applications faster
and easier, leverage investments in enterprise software and legacy systems, isolate existing
IT assets, and continuously monitor the entire enterprise.

OpenText AppWorks has the power and flexibility to digitize, automate and integrate
processes across functions, systems, machines and clouds. These processes can be
structured, or unstructured – giving you ultimate control to optimize your business’
performance and expand its reach. This innovative platform supports tight integration
between content and process to connect the right person, system or thing with the content it
needs at the right time.

OpenText AppWorks offers a single platform for process automation, case management
and low-code application development in the cloud. With less IT involvement, AppWorks
automates complex business processes, enables better decision-making and improves the
customer experience. It creates opportunities to re-engineer processes around customer
needs, deliver seamless customer experiences and adapt to changing customer expectations,
while improving operational efficiency and managing risk.

Key Features

• Create digital experiences faster

• Automate and optimize complex, structured and ad-hoc processes for efficiency

• Digitize, connect and manage information as a strategic asset to gain advantage

• Gain real-time insight through analytics, process monitoring and reporting

Benefits

• Design - Allow business users to create applications and define, modify and use embedded
processes

ENTERPRISE INFORMATION MANAGEMENT 12

 • Build - Create applications quickly at a lower cost using visual, drag-and-drop modeling
and pre- built building blocks

• Automate - Define, optimize and automate well-defined, structured and repeatable business
processes

• Manage - Integrate rules within business processes to standardize operational decisions and
ensure consistent execution of business policies

• Optimize - Gain visibility into real-time operations data to optimize activities to meet
business objectives

4.2 AppWorks Architecture

The OpenText architecture is multi-tiered and modular to provide organizations the highest level of

scalability, extensibility, openness, and security.

The AppWorks Platform is unique in that it has been designed as a single platform capable

of bridging three different approaches to digital process automation (see the three platform

layers in the diagram below):

• Low-code application development

• Case and process management

• SOA-based integration

ENTERPRISE INFORMATION MANAGEMENT 13

 Ope

n Text Architecture of Services and Applications

4.3 Design time architecture

The AppWorks Platform takes a model-driven approach to application development. A key principle

is that what you model is what you execute. All modeling activities are done in the Collaborative

Workspace (CWS), a browser-based integrated modeling environment allowing definition of all

kinds of models: data domain (entities), process, user interface, web services and so forth.

Application developers use a browser to create new models or modify existing ones. Most models

are represented graphically, featuring a responsive, rich user interface.

ENTERPRISE INFORMATION MANAGEMENT 14

 4.4 Runtime architecture
At runtime, the AppWorks Platform consists of a set of web service containers connected through a

SOA grid. The SOA grid provides three main facilities.

Routing of SOAP messages

The SOA is entirely SOAP-based. The services deliver their XML messages to the enterprise service

bus (ESB). Based on the service registry, stored in Lightweight Directory Access Protocol (LDAP)

directory called CARS, which knows the details of all the services. Given the required quality of

service and whether to use a reliable transport, it chooses a channel and delivers the message to the

recipient. The messages can be transferred over a variety of protocols, ranging from plain TCP/IP

sockets to message queues.

ENTERPRISE INFORMATION MANAGEMENT 15

 Load balancing

As the load increases, not everything can be handled in a single system, so multiple systems might

run the same service, thus sharing the load. The ESB has pluggable load balancing algorithms to

decide which service instance to address.

Failover

If one of the service instances fails, the load should immediately be moved to other instances and

business should go on as usual. This is taken care of by the failover features of the ESB.

The following diagram provides a 'bus view' of the AppWorks Platform:

The following illustration shows schematic view of a typical AppWorks Platform node:

ENTERPRISE INFORMATION MANAGEMENT 16

 4.5 AppWorks runtime components overview
This section provides further details on each of the platform components, introducing the following

platform capabilities:

• Entity modeling

• Business Process /Activity management

• User interfaces

• WS-AppServer

• Scheduling

• Standard compliances

• Security

4.5.1 Entity modeling :

The AppWorks Platform supports low-code application developers with an information-first

approach. The application developer starts by modeling the application’s domain and identifying

what the application needs (e.g. invoices and vendors). Then the developer adds properties to

describe each entity and define the relationships between the entities (e.g. each invoice would relate

to one vendor). Note that while defining an application domain does not require coding, it can get

ENTERPRISE INFORMATION MANAGEMENT 17

 complex. It is advisable to have people with appropriate technical skills involved in this part of the

process.

The AppWorks Platform extends this definition of an application’s domain to modeling the entire
application using a compositional approach of adding properties and relationships to an entity and
adding a large variety of building blocks to that entity. Each building block adds functionality to an
entity until the desired result is achieved. In practice, this aligns well with an agile/incremental
approach to application development.

4.5.2 Business Process /Activity Management:

The AppWorks Platform provides multiple options for coordinating user and system activities.
Application developers will use the tool(s) that best fit the needs of their application. In many
cases, a single application will use more than one. The Activity Management tools provided by
the AppWorks Platform include:

Business process management: AppWorks provides standard BPMN functionality, enabling the
creation of business processes that address well-defined, structured processes that include both
system and human activities.

Lifecycle building block: The Lifecycle building block enables an application developer to add
state-oriented activity management to an entity. This form of activity management is often referred
to as case management, and it works well in situations where the underlying business process is not
well-defined or must support user driven, ad-hoc, use cases.

Activity flow building block: The activity flow building block provides a tabular representation
of business processes, which is visually more intuitive to business users. It enables business users
to model simple processes.

ENTERPRISE INFORMATION MANAGEMENT 18

4.5.3 User interfaces:

The AppWorks Platform supports user interfaces of different kinds and technologies. This section
describes the low-code application runtime UI technology. In addition to this technologly,
developers can use any technology to create custom user interfaces.

The application runtime UI structures user interfaces through layouts with different types of panels
showing different information. For example, a layout can contain panels to show forms, lists, web
content, etc. List panels can list entities of different origin, including entities from various business
process management and content management systems. Through this, it is possible to design
appealing and informative user interfaces that enable users to access disparate systems and
applications using a consistent user interface.

There are two types of layouts: entity and home page. Entity layouts are used to display instances of
a specific entity and may contain panels that display various aspects of the current entity. Home page
layouts are launched with no entity and can only include panels that do not require an entity

4.5.4 Integrations – Enterprise information system connectivity :

Every enterprise uses one or more business applications and IT systems to manage the business of
the enterprise. Solutions developed with the AppWorks Platform nearly always integrate with
existing enterprise information systems, including ERP, content management, CRM and databases.
The AppWorks Platform provides two integration mechanisms, the entity oriented EIS mechanism
described above, and a generic API-oriented connectivity framework to connect to various systems
and applications. Based on this framework, the AppWorks Platform and the community around the
AppWorks Platform have developed a set of ready-made connectors for some of the most
commonly used IT systems.

The AppWorks Platform connectors act as an interface between the ESB layer and a specific
application, system or technology. It provides a two-way communication channel, which means
requests or messages from the ESB layer are converted to a format that is understandable by the
specific application or system and messages from the application are converted to SOAP
requests on the ESB.
ENTERPRISE INFORMATION MANAGEMENT 19
4.5.5 Document store:

Documents are usually stored in a content repository. The AppWorks Platform provides Document
store as the facility to work with any content repository. Any document, regardless of the content,
can be stored in these document stores. Documents can be added as attachments and retrieved later.
Documents can also be viewed, uploaded or downloaded.

Document store enables users to plug in a content repository so that any existing content repository
can be used. The AppWorks Platform can work with any content repository server that has exposed
its repository API according to the JSR 170 or CMIS specification.

The document store supports the following content repository types:

- Repository (proprietary, based on XDS, not supported for production usage)

- Apache Jackrabbit™
- Content Server
- Documentum
- OpenText™ Core
- Archive Center
- CMIS (any type of CMIS 1.1 compliant content repository)
- Custom plug-in implementation

4.5.6 Scheduling :

In a realtime business environment, the ability to trigger processes or applications based on

specific system events or at a specific time is a critical requirement. The AppWorks Platform
facilitates modeling of schedules that can trigger time-based actions, such as processes or web
service invocations. The AppWorks Platform provides an intuitive UI-based schedule modeler,
enabling modeling of different kinds of schedules that can be integrated into an application.

Schedules are generally of two kinds:

ENTERPRISE INFORMATION MANAGEMENT 20
 One-time schedule: These are executed only once

Type of
schedule Description

Run now Once created, this schedule is instantly executed

Duration This schedule can be set to execute after a specified duration

Repeating
schedule: These are triggered at specified periodic intervals, ranging from annually to hourly

Type of schedule Description

Hourly Recur at a specified time every hour

Daily Recur at a specified time every day

Weekly Recur at a specified time every week

Monthly Recur at a specified day every month

First day of the

month Recur at a specified time on the first day of every month

Last day of the

month Recur at a specified time on the last day of every month

First weekday of Recur at a specified time on the first weekday of every

the month month

Last weekday of Recur at a specified time on the last weekday of every

the month month

Fortnightly Recur at a specified time every 15th day

4.5.7 Technology Standard compliances:

The AppWorks Platform uses universally accepted standards, such as WSDL, XSD, XML and
SOAP. All consumers of the AppWorks Platform web services can use the "design by contract"
model for invoking these web services without having to worry about underlying implementations.
The AppWorks Platform is also WS-I Basic Profile compliant, so the services hosted on the
AppWorks Platform are completely compatible with different platforms. Developers can base their
functionality on the contract given by the WSDL and not worry about implementations

ENTERPRISE INFORMATION MANAGEMENT 21

 4.6 AppWorks Security
AppWorks provides the following authentication and authorizations:

4.6.1 Authentication:
Authentication is about establishing the identity of the user within the AppWorks Platform system in
a secure and trusted way. The AppWorks Platform has multiple options for user authentication.
Web server authentication
With web server authentication, the responsibility of authenticating the user is at the web server.
The web server handles user authentication and passes the user identity onto the AppWorks
Platform. Web server authentication can be handled in different forms:
 Basic, Digest, Domain Authentication (NTLM)

Certificate-based authentication

Certificate-based authentication adds an extra level of security to the platform as public key
infrastructure (PKI) is used to identify the user. Each user has a unique certificate, which will be used
for authentication in the web server. Only after the client certificate is validated is the user identity
passed on to the AppWorks Platform.

AppWorks Platform authentication

With AppWorks Platform authentication, user authentication is performed by the AppWorks

Platform Single Sign- On service (SSO) instead of by the web server. User authentication is based on
a username and password and, after validating a user, the SSO generates a signed SAML 1.1
assertion that states the user identity. This SAML 1.1 Assertion includes a SAML artifact that can be
used as a reference to the SAML assertion with each web service request from the front end, this
SAML artifact communicates in a web-browser session cookie. The web gateway looks up the
corresponding SAML assertion for the given SAML artifact and uses this internally in the AppWorks
Platform.

AppWorks Platform Authentication is an extensible system that allows custom login forms to be
used in the front end. The AppWorks Platform SSO service also has an extension mechanism, so that
one can also authenticate against other sources (e.g. Microsoft® Active Directory® or a database).

ENTERPRISE INFORMATION MANAGEMENT 22

 As complete user authentication is performed by the AppWorks Platform, authentication in the web
server needs to be disabled.

SAML authentication
Another form of non-web server authentication is based on SAML. Here, authentication is relayed to
an external service or identity provider (IDP) . The AppWorks Platform implements the SAML 2
Web browser SSO profile, which means the external IDP must support the SAML 2.0 standard.
OpenText Directory Services (OTDS) authentication
OpenText Directory Services (OTDS) is a product for user authentication and identity management
across OpenText products. OTDS provides the user with single sign-on across various OpenText
products. Users can be managed in OTDS and information about the identity of a user can be
exchanged between products that support OTDS.

OTDS supports various authentication methods, including Active Directory and two-factor
authentication. Given an authentication proof for a user in one product, OTDS can provide the
authentication proof of that same user for another product.

OAuth Web Service authentication

When an external application sends a SOAP or REST web-service request to the AppWorks
Platform, authentication information must be included with that request. The AppWorks Platform
supports different types of authentication information. One of these is OAuth access tokens provided
by OTDS.

ENTERPRISE INFORMATION MANAGEMENT 23

 The OAuth access token must be available in the Authorization HTTP header field of the request.
When the AppWorks Platform receives a request with an OTDS OAuth access token, it validates that
token with the help of the configured, trusted OTDS server. The access token contains a standard
JSON Web Token (JWT), with the user ID of the user, which is validated by the platform.

Advanced authentication features

Advanced authentication features, such as password policies, strong authentication and one-time-
passwords (OTP), are supported through the external IDP.

When an SSO user experience is needed, this can be implemented by configuring multiple
applications with the same identity provider. When all involved applications share an identity
provider, the user only needs to authenticate once at the identity provider and not on a per application
basis.

4.6.2 Authorization:
The AppWorks Platform has a role-based access system. By assigning roles to users, they get the set
of privileges as defined in entity security policies and service access control lists (ACLs) of these
roles. Roles can be composed of other roles.

Roles
A package role is defined during application development. It defines access to web services, data and
tasks. This is packaged as part of an application package and loaded to the Shared space. A call
handling application could, for instance, introduce an Escalation Manager role. The following role
types exist:
Is functional: Indicates whether the role is to be shown in organization model
Is internal: Indicates it should be skipped in the organizational modeler and user manager
Is technical: Indicates it should be skipped in the organizational modeler but shown in the user
manager

An organizational role is defined during runtime. It is created on an organization level and normally
aggregates package roles. An organization could define the roles Project Manager and Development
Manager and assign the application role Escalation Manager to both.
ENTERPRISE INFORMATION MANAGEMENT 24
 Access control lists

The ACL contains a set of authorizations or permissions that are added to a role or user. Each time a
user accesses a protected resource (e.g. a web service), an access control request is formulated and
matched against the complete set of ACLs for this user.

5 High Availability
Following are the expectations from High Availability perspective.

 The system will be available 24 hours per day, seven days per week the except maintenance

windows.

 High Availability is expected for OTDS, AppWorks, LDAPand Database in the Production.

5.1 High Availability qualities and requirements

Performance, scalability, and high availability (HA) are critical with make-or-break qualities
for any enterprise business application.
.

5.2 High Availability Architecture

The following diagram provides a visual representation of a typical IT landscape with real time
objects and the associated tiers.

ENTERPRISE INFORMATION MANAGEMENT 25

 The following table lists the mapping of tiers and objects.

The following table presents the core components involved in each activity.

5.3 Load Balancing

SAR intends to utilize F5 Load Balancer for load balancing. It is expected that F5 Load Balancer

will be able to load balance across servers in the primary data center. This is to be used to provide

HA for Content Server and other OpenText components.

ENTERPRISE INFORMATION MANAGEMENT 26

 5.4 SSL Encryption
As per agreement from SAR security team, HTTPS will be applied at Load Balancer level. So SAR
end user(s) will communicate with NLB over HTTPS and at NLB level, SSL will be offloaded and
subsequent calls to internal nodes will in HTTP.

 SSL configuration will be applied on prouction environments only as development and Test
environment does not have any NLB.

6 Backup Considerations
Opentext AppWorks has the following main components to take the backup :

1. AppWorks Installation and development directory

2. LDAP ( Light weight directory Access Protocol )

3. DB server

4. iHub report content

ENTERPRISE INFORMATION MANAGEMENT 27

 6.1 Backup components

6.2 Application directories backup

The primary installation directories and configuration for each of the applications should be backed-

up. The logs directories can be excluded but it is up to SAR to use their discretion to back up the

log's directories. OpenText does not provide any recommendation on backing up the application logs

or how long should they be retained. The exact install directory paths and logfile folders will be

determined at install time and documented within the build book

ENTERPRISE INFORMATION MANAGEMENT 28

 7 Environments
SAR has indicated that the following three environments will be deployed.

1. DEV

2. Test/QA

3. PRODUCTION

ENTERPRISE INFORMATION MANAGEMENT 29

 It is expected that all environments will include similar OpenText components/applications and will

be functionally equivalent. The QA environment will mirror the Production environment topology

but will be scaled down due to fewer user base. Production environments will include HA (High

Availability)

Environme Commen
Description Features
nt ts

DEV Development Functionalit

On-Prem
environment y
Test/QA An environment
mirroring
Production
environment Functionalit
however this On-Prem y
will be
provisioned with
less server
resources
PROD Production Functionalit
environment y
On-Prem High
Availability
Scaled

7.1 Development environment

7.1.1 Architecture

ENTERPRISE INFORMATION MANAGEMENT 30

7.1.2 Machine requirements

OpenText recommends allocating dedicated resources (CPU, RAM etc.) to the virtual machines hosting
the OpenText applications.

Server Nodes CPU RAM HD space Additional

Disk(s)

AppWorks – Dev 1 4 32 GB 100 GB  

C: 97.1GB
SQL Server 1 8 16GB  
D: 97.6GB

7.1.3 AppWorks Installation Details

This section is to provide the development environment details of process suite.

7.1.3.1 Server Details:

The below table provides the information of the hostname of the servers using.

Host Name and IP Address Description

ENTERPRISE INFORMATION MANAGEMENT 31
 ITEDMSAPPFDEV03 For AppWorks Platform server
(10.18.2.153)
ITEDMSDBDEV For AppWorks Platform DB server
(10.18.2.32)

7.1.3.1.1 AppWorks platform

The below table contains the details of the server in where Process Platform was installed.

Field Value
Server Name ITEDMSAPPFDEV03
Host name (FQN) ITEDMSAPPFDEV03.sar.com
Domain sar.com
IP Address 10.18.2.153
Server OS Windows Server 2016
Server Processor Intel(R) Xeon(R) CPU E5-2697 v4
Server Processor
Speed 2.30 GHz (2 processors)
RAM Size 32 GB
System Type 64 bit operating system, x64 based processor

7.1.3.1.2 Database

The below table contains the details of the server in where Database was installed.

Field Value
Server Host Name ITEDMSDBDEV
Host name (FQN) itedmsdbdev.sar.com
Domain sar.com
IP Address 10.18.2.32
Server OS Windows Server 2016
DB Version MSSQL 2019

7.1.3.2 Software Details

ENTERPRISE INFORMATION MANAGEMENT 32

 7.1.3.2.1 Java :

Java installed on the server with the following details:

Field Value
C:\Users\tulasiramk\Desktop\AppWorks
Software location
Installation
Install Folder C:\apps\Java
Java Version Open JDK 11
JAVA_HOME C:\apps\Java\jdk-11
Path C:\apps\Java\jdk-11\bin

7.1.3.2.2 TomEE :

TomEE installed on server with the following details:

Field Value
C:\Users\tulasiramk\Desktop\AppWorks
Software location
Installation
Install Folder C:\apps\TomEE
TomEE Version apache-tomee-8.0.6-plus
Oracle JDBC driver
Version mssql-jdbc-8.2.2.jre11.jar
Windows Service
name TomEE
TomEE User
Credentials
(Domain) TomEE / AppWorks@212
TomEE User
Credentials (Local) TomEE / Te@Sar@2030
Port 81
CATALINA_HOM
E C:\apps\TomEE

7.1.3.2.3 CARS

CARS installed on server with the following details:

ENTERPRISE INFORMATION MANAGEMENT 33

 Field Value
C:\Users\tulasiramk\Desktop\AppWorks
Software location
Installation
Install Folder C:\apps\OpenText\CARS
Instance Name AppWorksDEV
Current Version OpenText CARS 2.7
Server Port 6366
Suffix o=sar.com 
Directory
Manager cn=Directory Manager,o=sar.com
Installation Type Network enabled
CARS Password dmanager
LDAP
Configuration
Management cn=admin,cn=config
LDAP
Configuration
Management
Password dmanager

7.1.3.2.4 License Key

License key applied on server with the following details:

Field Value
Customer Name SAUDI ARABIAN RAILWAY
Site Name  SAR AWP Dev
Host ITEDMSAPPFDEV03.sar.com
bf3b5eb9-6eab0b6e-cc39bf32-587a99af-
License Key
3320af85-f56061b6-32276e02-6b9cd717

7.1.4 AppWorks Platform access details :

AppWorks Platform installed on server with the following details:

Field Value
Software location C:\Users\tulasiramk\Desktop\AppWorks Installation
Installation Folder C:\apps\OpenText\AppWorksPlatform\

ENTERPRISE INFORMATION MANAGEMENT 34

 Instance Name AppWorksPlatform
Current Version AppWorks _ Platform_21.2
DB Connection Type MSSQL
Installation Type Network Enabled
Process Platform Port
Number 81
JMX User credentials admin/admin
Cordys Setup User sysadmin/ sysadmin
Process Platform URL http://10.18.2.153:81/home/system
http://10.18.2.153:81/home/system/app/processExperience/web/
Process experience URL
perform
Process experience Admin
URL http://10.18.2.153:81/home/system/app/admin/web/config#

7.2 Test/QA environment

7.2.1 Architecture

7.2.2 Machine requirements

OpenText recommends allocating dedicated resources (CPU, RAM etc.) to the virtual machines

hosting the OpenText applications.

ENTERPRISE INFORMATION MANAGEMENT 35

 Server Nodes CPU RAM App(D) Logs (L) Additional

Disk(s)

AppWorks –
1 4 32 50 30  
Dev

iHub 1 4 8 50 50  

SQL Server 1 8 16 60   800

7.2.3 AppWorks Installation Details

This section is to provide the development environment details of AppWorks .

7.2.3.1 Server Details

The below table provides the information of the hostname of the servers using.

Host Name and IP Address Description

TBD For AppWorks Platform server
TBD For AppWorks Platform DB server

7.2.3.1.1 Process Suite platform

The below table contains the details of the server in where Process Platform was installed.

Field Value
Server Name TBD
Host name (FQN) TBD
Domain TBD
IP Address TBD
Server OS TBD
Server Processor TBD
Server Processor
Speed TBD
RAM Size TBD
System Type TBD

ENTERPRISE INFORMATION MANAGEMENT 36

 7.2.3.1.2 Database

The below table contains the details of the server in where Database was installed.

Field Value
Server Host Name TBD
Host name (FQN) TBD
Domain TBD
IP Address TBD
Server OS TBD
DB Version TBD

7.2.3.2 Software Details

7.2.3.2.1 Java

Java installed on the server with the following details:

Field Value
Software location TBD
Install Folder TBD
Java Version TBD
JAVA_HOME TBD
Path TBD

7.2.3.2.2 TomEE

TomEE installed on server with the following details:

Field Value
Software location TBD
Install Folder TBD
TomEE Version TBD
Oracle JDBC driver
Version TBD
Windows Service
name TBD
TomEE User
Credentials (Domain) TBD
TomEE User
Credentials (Local) TBD
Port TBD

ENTERPRISE INFORMATION MANAGEMENT 37

 CATALINA_HOME TBD

7.2.3.2.3 CARS

CARS installed on server with the following details:

Field Value
Software location TBD
Install Folder TBD
Instance Name TBD
Current Version TBD
Server Port TBD
Suffix TBD
Directory Manager TBD
Installation Type TBD
CARS Password TBD
LDAP Configuration
Management TBD
LDAP Configuration
Management
Password TBD

7.2.4 AppWorks License Key

License key applied on server with the following details:

Field Value
Customer Name TBD
Site Name TBD
Host TBD
License Key TBD

7.2.5 AppWorks Platform access details

OpenText Process Platform installed on server with the following details:

ENTERPRISE INFORMATION MANAGEMENT 38

 Field Value
Software location TBD
Installation Folder TBD
Instance Name TBD
Current Version TBD
DB Connection Type TBD
Installation Type TBD
Process Platform Port
Number TBD
JMX User credentials TBD
Cordys Setup User TBD
Service Account User TBD
Process Platform URL TBD
Process experience
URL TBD
Process experience
Admin URL TBD

7.3 Production environment

7.3.1 Architecture

AppWorks platform high availability/IP Load balancer installation example.

ENTERPRISE INFORMATION MANAGEMENT 39

7.3.2 Machine requirements

OpenText recommends allocating dedicated resources (CPU, RAM etc.) to the virtual machines
hosting the OpenText applications.

Server Nodes CPU RAM App Logs Additional

(L) Disk(s)
(D)

AppWorks – Dev 2 4 32 50 100  

Search & Index 1 4 12 50 100  

SQL Server 1 8 16 60   800

7.3.3 AppWorks Installation Details

This section is to provide the development environment details of process suite.

7.3.3.1 Server Details

The below table provides the information of the hostname of the servers using.

Host Name and IP Address Description

TBD For AppWorks Platform server

ENTERPRISE INFORMATION MANAGEMENT 40

 TBD For AppWorks Platform DB server
7.3.3.1.1 Process Suite platform

The below table contains the details of the server in where Process Platform was installed.

Field Value
Server Name TBD
Host name (FQN) TBD
Domain TBD
IP Address TBD
Server OS TBD
Server Processor TBD
Server Processor Speed TBD
RAM Size TBD
System Type TBD

7.3.3.1.2 Database

The below table contains the details of the server in where Database was installed.

Field Value
Server Host Name TBD
Host name (FQN) TBD
Domain TBD
IP Address TBD
Server OS TBD
DB Version TBD

7.3.3.2 Software Details

7.3.3.2.1 Java

Java installed on the server with the following details:

Field Value
Software location TBD
Install Folder TBD
Java Version TBD
JAVA_HOME TBD
Path TBD

ENTERPRISE INFORMATION MANAGEMENT 41

 7.3.3.2.2 TomEE

TomEE installed on server with the following details:

Field Value
Software location TBD
Install Folder TBD
TomEE Version TBD
Oracle JDBC driver
Version TBD
Windows Service
name TBD
TomEE User
Credentials (Domain) TBD
TomEE User
Credentials (Local) TBD
Port TBD
CATALINA_HOME TBD

7.3.3.2.3 CARS

CARS installed on server with the following details:

Field Value
Software location TBD
Install Folder TBD
Instance Name TBD
Current Version TBD
Server Port TBD
Suffix TBD
Directory Manager TBD
Installation Type TBD
CARS Password TBD
LDAP Configuration
Management TBD
LDAP Configuration
Management Password TBD

7.3.4 AppWorks License Key

License key applied on server with the following details:
ENTERPRISE INFORMATION MANAGEMENT 42
 Field Value
Customer Name TBD
Site Name TBD
Host TBD
License Key TBD

7.3.5 AppWorks Platform Access details

OpenText Process Platform installed on server with the following details:

Field Value
Software location TBD
Installation Folder TBD
Instance Name TBD
Current Version TBD
DB Connection Type TBD
Installation Type TBD
Process Platform Port
Number TBD
JMX User credentials TBD
Cordys Setup User TBD
Service Account User TBD
Process Platform URL TBD
Process experience
URL TBD
Process experience
Admin URL TBD

ENTERPRISE INFORMATION MANAGEMENT 43

 8 Software Version Details

8.1 Opentext Software Versions

The following software versions will be deployed as part of the implementation to all environments
like Dev , QA and Production

S.N Opentext Product Version Comments

o
1 AppWorks 21.2
2 iHub 21.1
3 xECM 21.2
4 OTDS 21.2

8.2 Third-Party Software versions

This section details the version of the 3rd party software required for Development , UAT and
Production servers

3rd Party software

S.N Opentext Product Version Comments

o
1 Java OpenJDK
11.0.7
2 Apache Tomcat 9.0.44 (64 bit)
3
4

8.3 Patches
OpenText will install the latest patch set at the time of implementation and patches applied will be
detailed in the relevant build guides. OpenText will do a formal handover of the solution post
implementation where this will be fully explained. Patching is deployed using AppWorks deployer .
ENTERPRISE INFORMATION MANAGEMENT 44
 9 Conclusion
This document provides OpenText AppWorks architecture related requirements for SAR proposed

OpenText AppWorks environment to scale and size according to their probable needs. These

architecture requirements are based upon several assumptions and data provided by SAR.

The common theme throughout this document is one of providing additional factors of safety in

calculating required capacity to address downstream unknowns. AppWorks system is a constantly

changing system, especially with new users and new business process introduced on a regular basis;

monitoring is essential for smooth growth.

As the systems evolve and usage patterns are further refined, or user requirements change, it may be

necessary to tweak any architecture accordingly. The flexible architecture presented here will allow

for further direct scaling and easy configuration to be conducted transparently, whilst maintaining

high performance standards for an active and evolving user base.

10 Acceptance of Deliverable

This approval represents that this document is an accurate representation, to the best of the approver's

knowledge, of the functionality from an end-user's perspective.

The above deliverable has been reviewed and accepted by SAR.

SAR:

________________________________ _______________________________

ENTERPRISE INFORMATION MANAGEMENT 45

 Name (printed) Signature

Date

About OpenText
OpenText enables the digital world, creating a better way for organizations to work with information, on premises or in the cloud.
For more information about OpenText (NASDAQ: OTEX, TSX: OTC) visit opentext.com.

Connect with us:

OpenText CEO Mark Barrenechea’s blog

Twitter | LinkedIn | Facebook

ENTERPRISE INFORMATION MANAGEMENT 46

 AppWorks - Architecture Design Specifications

www.opentext.com/contact
Copyright © 2017 Open Text SA or Open Text ULC (in Canada).
All rights reserved. Trademarks owned by Open Text SA or Open Text ULC (in Canada).