Nothing Special   »   [go: up one dir, main page]

About OPENTEXT

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 4

About OPENTEXT

 Content Server 10.5.0, by OpenText Corporation, is the Enterprise Content


Management software being implemented at Suncor Energy Inc. as replacement for
old version OpenText livelink 9.7.1.

 Content Server is a Web-based application for storing, sharing, and distributing


information. It provides a collaborative work environment that will help manage
documents and project information, improve business processes, and share
information.
 Content Server is designed to help:

 Organize documents and other work items in a central, permission-controlled


location.
 Share, find, and keep track of information.
 Revise documents and other information in a version-controlled environment.
 Manage and simplify business processes by creating and using Workflows.
 Communicate news and other information to other members of the
organization.

Architecture:

 It is a multi tier architecture which has


o Access Tier (OTDS)
o Application Tier (Frontend, ADMIN, Agents, Blazon),
o Data Tier (DB, EFS, Archive)
 The Content Server architecture consists of

 Front-End servers that serve user requests


 Admin servers that manage the indexing and search processes
 Agent server that hosts OpenText agents
 Blazon Server(s) that provide rendition services
 Brava! Server(s) that provide view and Redline capabilities
 Oracle database that stores metadata
 external file storage along with Archive (OTAS) Server to store versioned
content
Integrations:

 XECM is a tool by OpenText to provide seamless integration with SAP.


 Blazon by OpenText is for rendering and the document conversion tool. which
converts MS Office documents into .PDF files
 Brava for OpenText Content Server provides the Document viewer functionality for
Drawings and other mimetypes.
 Adlib PDF for OpenText Content Server is third party module which converts MS
Office documents into .PDF files.
 eB and PW are integrated with CS10 for moving files in and out.
Security & Identity and Access Management:

 OpenText Directory Services (OTDS) 10.5.0 manages user and group identity
information for OpenText components.
 OTDS contains services for identity synchronization and provides single sign on for
other OpenText components.
 Authentication to Content Server is maintained by Active Directory Groups, users are
added to an AD group which is synced to OTDS to provision users in Content Server.
 SSL Encryption is configured on Front end Servers in all environments to protect user
passwords from being sent in clear text. Agent and Admin instances do not currently
have encryption enabled.
 Application access has been secured using SSL certification, hence protecting application
against any unwanted interception. Content Server tool itself also have string
mechanism like Cookie Encryption etc to protect information and application.
 Content server provides a strong access control system. All information stored is
accessible to end user strictly based on their permission level.
 Access to Support Group, Higher privileges, Exception privileges are all documented and
audited on regular basis for need and validity. Also, system passwords are safely
guarded in Password Vault and access to that is safeguarded via documented process
and stringent approval process. System Password are changed on regular basis as a
maintenance task to avoid any gaps.

Backup & Restore:

 For Content Server10.5 application at Suncor four types of backups will be carried out:
Windows Server backup, EFS backup, and Database backup and Index Backup.
 Index Backup will be carried out by Backup Manager which is present in the Content
Server Application.
Failover & Disaster Recovery:

 Disaster Recovery includes


o Impact and risk assessment.
o Planning and appropriate solution implementation.
o Validation through regular exercises
o regulatory compliance and audits.

Monitoring & Health Checks:


 Content Server being a Platinum application has high availability SLA. It is important to have
constant monitoring of the system to avoid any outages and get early sign of alert to prevent
outages.

 For CS10 Automated monitoring to monitor application has been set up using SCOM, which
monitors application from different perspective like Directory space, CPU, Memory, High
CPU or Memory using transaction etc.

 There are also Manual checks done by support team on daily/weekly basis to make sure of
system availability, functionality and performance, Support team maintains a record of such
monitoring
Component What it checks

Free space Checks that the OTHOME partition has more than X free space.
Optionally if it is below the limit old logs can be automatically purged and logging levels can be
dialed down to try and avoid a 100% full situation

Directory Watch Add a customizable watch to any directory to warn if there is a buildup of too many files (by
count, size, or time). This is useful for any directories being used as a temporary queue for
processing like iPool directories, xmlimport, etc.

Running Requests Warns if there are user requests running for over X seconds and/or if there is a queue depth over
Y requests

Trace files Alerts if there are more than X trace files in the log’s directory

EFS For each Content Server checks that all EFS storage providers are readable and writable. From the
primary server we will also check free space.

This option will only display if EFS storage providers exist.

Archive Server For each Content Server test attempt to connect to Archive Server (no content is read/written),
also check the easp_dsh.log file (if logging enabled) for excessive errors reported from end user
requests to read/write to the Archive Server.
This option will only display if Archive Server storage providers exist.

Database Ensure that the Content Server can connect and perform a basic select/insert/delete to the
database

Admin Servers Checks that all AdminServers are up and not reporting any process errors (indexing, dcs,
memcached, etc)
Optional: If process errors encountered Informant can attempt to fix the issue.

Search All Search Federators and Search Engines are running and that a simple search of the Enterprise
search slice can be performed

Search Backups Checks that the search backup location (if defined) for each partition has been written to in the
last X days.
This option will only display if search backups have been configured.

Search Extractor Warns if dtreenotify has more than X rows or if there is new content (ntype=1) in the queue older
than Y.

Agents Warns if notifyevents has more than X rows, if there are events in the queue older than Y, or if
there are agents that are more than Z seconds past their next run time

CS Directory If the Directory Services module is installed and there are synchronization sources defined, then it
Services will alert if last sync completion was not successful.
This option will only display if CS Directory Services module is installed.
Cluster Thread Realtime view across the cluster of what requests are currently running. Does not require a user
Stauts thread from each server to view, so good for when a server is unresponsive to be able to see what
requests are running, who is running them, and for how long have they been running.

Patches Tracks installation/removal of Content Server patches on each server. Can alert if there are
discrepancies across servers.

Change Control Checks if changes have occurred to patches, opentext.ini, or kini settings but have not yet had a
change comment added. Configuration settings which have been “muted” are excluded. There is
a 24-hour grace period after a change is detected before an alert is sent.

Roles and Responsibilities:


o Application Monitoring / Health checks
o Resolving the technical queries of the Users
o Handling the High Priority issues and application outages
o Managing the integration of different applications and resolving the quires
o Working on multiple environments like prd/qut/dev/trn
o Creating and maintaining the Knowledge base
o Maintaining the backups and the Disaster recovery plans
o Applying the monthly patches / implementing the changes
o Reporting the software bugs and user suggestions to the SME /higher
management.
o Working with multiple teams to ensure the stability, continuity and high
availability of the application.

You might also like