DELMIA Apriso 2020 Administration Guide

DELMIA Apriso

®2021 Dassault Systèmes. Apriso, 3DEXPERIENCE, the Compass logo and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA, DELMIA, SIMULIA, GEOVIA, EXALEAD, 3D VIA, BIOVIA, NETVIBES, and 3DXCITE
are commercial trademarks or registered trademarks of Dassault Systèmes or its subsidiaries in the U.S. and/or other countries. All other trademarks are owned by their respective owners.
Use of any Dassault Systèmes or its subsidiaries trademarks is subject to their express written approval.
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 2

Contents
1 Introduction 4
2 DELMIA Apriso Architecture 5
3 Configuration Files 6
3.1 Rules of Configuration Files Usage 6
3.2 Configuration Files Edition 6
3.3 Configuration Variables 7
4 Monitoring 10
4.1 Health Monitoring 10
4.1.1 Information Published by DELMIA Apriso for Monitoring Purposes 10
4.1.2 Microsoft System Center Operations Manager 10
4.1.3 XML Messages 10
4.2 Performance Monitor Counters 10
4.2.1 Apriso Group 11
4.2.2 Apriso JobExecutor Group 18
5 Diagnostics 21
5.1 Diagnostic Logging 21
5.2 Event Log 21
5.3 Response for Common Critical Actions 21
6 Deploying Service Packs 23
6.1 Assumptions 23
6.2 Service Pack Installation Process 23
6.3 Uninstallation 23
6.4 Upgrading Client Computers 24
6.5 Running Post-Upgrade Utility 24
6.6 Installing in Silent Mode 24
6.7 Third-Party Service Pack Installation 25
7 Upgrade to New Versions 26
8 Database Maintenance 27
8.1 Gathering Oracle Database Statistics 27
8.2 Archiving 27
8.3 Backup and Restore 28
9 Miscellaneous/Troubleshooting 29
9.1 Modifying Session Timeout 29
9.2 Modifying Data Lifetime for Menu Data (Menu Items) 29
9.3 Access Rights to the Apriso Logging Folder 29
9.4 Disabling Antivirus Scanning for Temporary Folder 30
9.5 Setting the Optimizer Mode for the DELMIA Apriso Database 30
9.6 Connectivity Problems Due to Proxy Configuration 30
9.7 ClickOnce Applications Failing to Start when Root Certificates are Missing 32
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 3

9.8 Session Sharing 33

9.9 Running Apriso Services Using a Domain Account 33
9.10 Avoiding Issues Concerning the UTC Function in Oracle 34
9.11 DELMIA Apriso Portal Display Issue When Using HTTPS 35
10 References 36

Figures
Figure 1 DELMIA Apriso architecture 5
Figure 2 DELMIA Apriso Configuration Manager 7
Figure 3 DELMIA Apriso Archiving 28
Figure 4 Adding a DELMIA Apriso server to the Proxy Settings Exceptions list 32
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 4

1 Introduction
This document is a guide to the administration of the DELMIA Apriso server. Descriptions of
several DELMIA Apriso tools are given to provide a general overview of their scope. To get
detailed information, referring to the appropriate Implementation Guide, Technical Guide, or
Help is recommended. A document reference list is provided in 10 References.
It is recommended that the individual(s) responsible for administering the DELMIA Apriso
servers have knowledge in database administration as well as in the administration and
configuration of Microsoft Windows servers.
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 5

2 DELMIA Apriso Architecture

Figure 1 DELMIA Apriso architecture

The diagram above depicts the different components installed in DELMIA Apriso and located
both on the server and the client. It also shows the interactions between them.
The parts of the above diagram marked with green may exist on several different machines,
and they can be duplicated (cluster machine) or exist on one computer together.
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 6

3 Configuration Files
3.1 Rules of Configuration Files Usage
The configuration of DELMIA Apriso is stored in configuration files in the XML format. The files
contain the database connection data, the log file configuration, and other important
information. Most of the settings are set in files that are located in the special
CentralConfiguration folder. The folder contains the CentralConfiguration.xml file, which keeps
most of the settings, and other files that can adjust and modify the other functionalities (e.g.,
Business Integrator is configured within XMLManager_*.xml files). Each service (e.g., Job
Executor) and component has its own .config configuration file, which references
CentralConfiguration.xml and uses the CentralConfiguration.xml settings. You therefore only
need to edit one file, which makes the configuration simpler and easier. It is also possible to
override the Central Configuration settings by copying a specific section (settings) to the local
.config file. This is used in specific cases when the same configuration cannot be applied
everywhere.

After the modification of a .config file, it is necessary to restart the component it belongs
to in order for the changes to take effect.

The changes made on one machine must be applied to all the nodes in a cluster.
For details on the configuration options for individual DELMIA Apriso components, please
refer to the appropriate Implementation Guides.

3.2 Configuration Files Edition

In order to introduce any changes in the configuration files, using the DELMIA Apriso
Configuration Manager is recommended, as it writes the new values back to the configuration
files.
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 7

Figure 2 DELMIA Apriso Configuration Manager

For more information on the DELMIA Apriso Configuration Manager functionality, refer to
Configuration Manager Help.
Entries that are not used frequently are not covered by the Configuration Manager. In that
case, you need to make the changes manually (however, this is not recommended action).

3.3 Configuration Variables

The configuration variables organize DELMIA Apriso configuration. They enable changing
values of different settings only in one place. For example: every occurrence of application
server or Web server address is replaced with a configuration variable (e.g. ${AppAddress} and
${WebAddress}). The variable refers to a value that is defined in one place by AppAddress and
WebAddress configuration variable (DeploymetInfo.xml). This means that in order to change the
NLB virtual address you should change the value only in one place.
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 8

The variables are stored in the DeploymetInfo.xml file (<drive>\Program Files\Dassault

Systemes\DELMIA Apriso 2020\Website\CentralConfiguration). There are two types of configuration
variable:
Global variables – are used by every node in a cluster configuration and are defined in the
<configurationVariables>section of the DeploymentInfo.xml file.

<configurationVariables>
<variable name="Scheme" value="http"></variable>
<variable name="AppAddress" value="[servername]"></variable>
<variable name="WebAddress" value="[servername]"></variable>
<variable name="ProgramFilesPath" value="C:\Program Files\Dassault Systemes\DELMIA
Apriso 2020\"></variable>
<variable name="AprisoTempPath" value="C:\Temp\AprisoTemp"></variable>
<variable name="WebRootURL" value="http://${WebAddress}/Apriso"></variable>
<variable name="WebSitePath" value="${ProgramFilesPath}WebSite\"></variable>
</configurationVariables>

Key Description
Scheme The protocol used by the DELMIA Apriso server (http or https).
AppAddress DNS registered network name (or absolute domain name) resolving to the
local IP address of DELMIA Apriso web server configured with Web
Server Role. The parameter can be changed in Configuration Manager
(System Settings tab).
WebAddress DNS registered network name (or absolute domain name) resolving to the
local IP address of the DELMIA Apriso application server configured with
Application Server Role. The parameter can be changed in the
Configuration Manager (System Settings tab).
ProgramFilesPath The disk path of the DELMIA Apriso Product.
AprisoTempPath The path to the Web Services' temporary directory.
WebRootURL The root URL of DELMIA Apriso Product.
WebSitePath The disk path of the DELMIA Apriso Product.
Local variables – can be defined by the user. They can override global variable settings.
They can be defined for a specific node if it is needed, in the <configurationVariables>
section inside the <machines> section. The <configurationVariables> section needs to be
added manually to the DeploymentInfo.xml file.
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 9

<machines>
<machine name="[servername]" role="Web">
<configurationVariables>
<variable name="WebAddress" value="[servername]"></variable>
</configurationVariables>
…
</machine>
</machines>

Configuration variables are beneficial when it comes to:

Changing such values in the configuration – only one change is required
Modifying DELMIA Apriso configuration by Service Packs – there is no necessity of running
the Cluster Configuration Wizard after Service Pack installation unless it is required
It is an essential mechanism for supporting cluster DELMIA Apriso installation

Configuration Variable Usage Example

The application server address and Web server address can be easily changed with the use
of AppAddress and WebAddress configuration variables directly in the DeploymentInfo.xml file.
You need to refer to these variables using the following syntax “${WebAddress}“ and
“${AppAddress}“ in the System Settings tab (Figure 2 DELMIA Apriso Configuration Manager) of
the DELMIA Apriso Configuration Manager (see Configuration Manager Help).

When changing WebAddress you should regenerate ClickOnce applications' manifests

(run Publish All Apriso Applications via ClickOnce.bat found in: <drive>\Program
Files\Dassault Systemes\DELMIA Apriso 2020\WebSite\Downloads\ClickOnce Tools to
republish the ClickOnce manifests).
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 10

4 Monitoring
4.1 Health Monitoring
4.1.1 Information Published by DELMIA Apriso for Monitoring
Purposes
Information that requires immediate administrative attention is published in the following
places:
Apriso logs
The Windows Event Log
Windows Performance Counters viewable by the Windows Performance Monitor
If a log entry published in the Apriso log is of the FATAL type, a duplicate is published in the
Windows Event Log. Information published in both the Event Log and Performance Monitor
can also be monitored in the Microsoft System Center Operations Manager.

4.1.2 Microsoft System Center Operations Manager

Usage of the Microsoft System Center Operations Manager (SCOM) is optional, as the system
can be fully monitored using Performance Monitor and Event Viewer. However, using SCOM
facilitates system monitoring and makes many administrative actions easier or even
automatic.
DELMIA Apriso delivers the SCOM monitoring package and documentation through the
services/support offering. Please contact your services/account representative to get more
information about the SCOM deliverable and to acquire it.
For a detailed description of the counters and events that require specific administrator
attention, refer to 4.2 Performance Monitor Counters.

4.1.3 XML Messages

XML transactions within DELMIA Apriso can be monitored via the Job Scheduler:XML
Messages screen in DELMIA Apriso Desktop Client. The messages that failed are listed there
and can be edited and re-submitted.
For more details, refer to the Business Integrator – Configuration Guidelines Technical Guide.

4.2 Performance Monitor Counters

DELMIA Apriso publishes the following performance counter values for monitoring in the
Windows Performance Monitor.
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 11

Restarting the server after the first execution of the process that creates Performance
Counters is recommended.

4.2.1 Apriso Group

Counter Description Meaning
Business The average A Business Transaction is a single processing unit
Transaction Business performed by DELMIA Apriso. It mainly contains
Duration Transaction database transactions, but it can also include
execution time (in additional processing as needed. The duration of the
milliseconds). transaction should be as short as possible. Lower
values denote better performance. Higher values (>2
seconds) indicate that the system is experiencing
performance issues or the existence of transactions
that, by design, take a long time to execute.
Business The number of The number of Business Transactions executed per
Transactions / Business second. Higher values indicate that more transactions
sec Transactions are being executed and that the system performance
executed per is good. Lower values mean that the system is
second. experiencing performance issues (e.g., the system is
fully loaded) or user inactivity. The actual numbers
depend on the system configuration, functionality, and
load.
Client Request The average client The time required to process a Windows client
Duration request execution request on the server. This does not include the time
time. Client requests required to deliver the request and response via the
are requests raised network. The duration of the request should be as
by the client-side UI short as possible. Lower values indicate better
and served by the performance. Higher values (>2 seconds) indicate that
business logic layer the system is experiencing performance issues
components on the resulting from a poor client UI response time.
server via remoting
(in milliseconds).
Client The number of client The number of client requests executed per second.
Requests / sec requests executed Higher values indicate that more requests are being
per second. Client executed and that the system performance is good.
requests are Lower values mean that the system is experiencing
requests raised by performance issues (e.g., the system is fully loaded) or
the client-side UI user inactivity. The actual numbers depend on the
and served by the system configuration, functionality, and load.
business logic layer
components on the
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 12

server via remoting.

Database
Database The average The time required to perform an average atomic
Operation database operation database operation. All database operations (reading
Duration execution time. A and writing) are shown. The duration of an operation
database operation should be as short as possible. Lower values indicate
is the most atomic better performance, while higher values (>2 seconds)
(read or write) suggest system performance issues.
operation performed
on a database (in
milliseconds).
Database The number of The number of database operations executed per
Operations / sec database operations second. A high value indicates that more operations
executed per are being executed and that the system performance
second. A database is good. Lower values mean that the system is
operation is the experiencing performance issues (e.g., the system is
most atomic (read or fully loaded) or user inactivity. The actual numbers
write) operation depend on the system configuration, functionality, and
performed on a load.
database (in
milliseconds).
Database The number of The number of database reads executed per second.
Reads / sec atomic database Higher values indicate that more reads are being
reads executed per executed and that system performance is good. Lower
second. values mean that the system is experiencing
performance issues (e.g., the system is fully loaded) or
user inactivity. The actual numbers depend on the
system configuration, functionality, and load.
Database The average The time required to perform an average atomic
Transaction database database transaction. All the database transactions
Duration transaction (committed and rolled back) are shown. The duration
execution time (in of a transaction should be as short as possible. Lower
milliseconds). A values indicate better performance, while higher
database values (>2 seconds) suggest system performance
transaction is a set issues or poor operation design.
of atomic database
operations executed
together as one
piece of logic.
Database The number of The number of database transactions executed per
Transactions / started database second. Higher values indicates that more
sec transactions per transactions are being executed and system
performance is good. Lower values mean that the
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 13

second. A database system is experiencing performance issues (e.g., the

transaction is a set system is fully loaded) or user inactivity.
of atomic database
The actual numbers depend on the system
operations executed
configuration, functionality, and load.
together as one
piece of logic.
Database The number of The number of successful database transactions
Transactions committed database (committed) performed by the system per second.
committed / sec transactions per
Higher values indicate that more transactions are
second. A database
being executed and that the system performance is
transaction is a set
good. Lower values mean that the system is
of atomic database
experiencing performance issues (e.g., the system is
operations executed
fully loaded) or user inactivity. The actual numbers
together as one
depend on the system configuration, functionality, and
piece of logic.
load.
Database The number of The number of failed database transactions (rolled
Transactions rolled back back) performed by the system per second. The value
rolled back / sec database should be as close to zero as possible. Higher values
transactions per indicate that many transactions are being rolled back
second. A database as a result of processing errors. The actual numbers
transaction is a set depend on the system configuration, functionality, and
of atomic database load.
operations executed
together as one
piece of logic.
Database writes The number of The number of database writes performed by the
/ sec atomic database system per second. Higher values indicate that more
writes executed per writes are being executed and system performance is
second. good. Lower values mean that the system is
experiencing performance issues (e.g., the system is
fully loaded) or user inactivity. The actual numbers
depend on the system configuration, functionality, and
load.
Portal
Portal Request The average Web The time required to process a Web client request on
Duration Portal request the server. This does not include the time required to
execution time (in deliver the request and response via the network. The
milliseconds) duration of a transaction should be as short as
possible. Lower values indicate better performance,
while higher values (> 2 seconds) suggest system
performance issues resulting from a poor client Web
UI response time.
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 14

Portal Request / The number of Web The number of Portal requests. Higher values indicate
sec Portal requests that more writes are being executed and system
executed per performance is good. Lower values mean that the
second. system is experiencing performance issues (e.g., the
system is fully loaded) or user inactivity. The actual
numbers depend on the system configuration,
functionality, and load.
Background Job Processing
Scheduler The number of The number of currently active threads used by Job
Active Executor active (busy) Scheduler to execute jobs. The value is also equal to
Threads execution threads. the number of currently executed jobs.
The maximum value is equal to the limit of the threads
defined in Central Configuration. It should stay below
the maximum limit the majority of the time. Lower
values indicate a good performance, and very low
values (close to zero) indicate that a small number of
threads are currently being used to execute the jobs.
Higher values (close to the limit defined in Central
Configuration) indicate that most of the available
threads are busy and additional requests (new jobs)
may need to wait to be executed.
Scheduler Job The average delay The delay in the execution of a job compared to the
Execution between the time a scheduled time (or the job creating time for immediate
Delay job has been jobs). The delay should be as small as possible.
scheduled and the Lower values indicate a good performance and that
time it was Job Scheduler is starting job executions as
published for scheduled. Higher values (>1 sec) indicate that Job
execution (in Scheduler is delaying job executions as a result of
milliseconds). performance issues.
Scheduler Job The average job The time required to process an average job in Job
Execution execution time (in Scheduler. The duration of the job execution should
Duration milliseconds). be as short as possible. Lower values indicate better
performance. Long durations (>2 seconds) indicate
performance issues in the system or the existence of
jobs that by design take a long time to execute.
Scheduler Job The number of The overall number of processed jobs since the last
Executions executed j obs. restart (both successful and failed jobs are shown).
The value of the counter should increase
continuously. When the value does not increase, this
is an indication that jobs are not being processed (that
is, there is an issue in Job Scheduler) or jobs are not
being created. The actual speed of increase depends
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 15

on the system configuration, functionality, and load.

Scheduler Job The number of jobs The number of Scheduler Job Executions per second.
Executions / executed per Higher values indicate that more jobs are being
sec second. executed and the system performance is good. Lower
values mean that the system is experiencing
performance issues (e.g., the system is fully loaded) or
user inactivity. The actual numbers depend on the
system configuration, functionality, and load.
Scheduler Job The number of failed The overall number of failed jobs since the last restart.
Executions jobs. The value should be as close to zero as possible and
(failed) should not grow. Lower values indicate a good
performance, while higher values indicate that many
jobs are failing during the execution as a result of
errors in processing.
The actual numbers depend on the system
configuration, functionality, and load.
Scheduler Job The number of failed Shows the number of failed job executions per
Executions jobs per second. second. Has the same meaning as the Scheduler Job
(failed) / sec Executions (failed) counter above.
Scheduler Job The number of Shows the overall number of successful jobs since the
Executions successfully last restart. The value of this counter should increase
(successful) executed jobs. continuously. When it does not, one of the following is
occurring:
Jobs are not being processed (that is, there is an
issue in Job Scheduler)
Jobs are being processed but are failing
New jobs are not being created (as in, there is a
small load on the system)
The actual numbers depend on the system
configuration, functionality, and load.
Scheduler Job The number of The number of successful job executions per second.
Executions successfully Has the same meaning as the Scheduler Job
(successful) / executed jobs per Executions (successful) counter above.
sec second.
Scheduler new The number of new The number of new jobs created by DELMIA Apriso
jobs jobs recently loaded and discovered by Job Scheduler during the last load.
by Job Scheduler
The value should reflect number of new background
service.
jobs created by the system. The actual numbers
depend on the system configuration, functionality, and
load.
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 16

Scheduler The number of jobs The number of jobs that are ready for execution
pending Jobs waiting for (schedule time occurred) and waiting to be executed.
execution. The jobs Lower values (<10) indicate that Job Scheduler is
might be waiting for executing all the jobs as they arrive, which is normal
the Synchronization (as in, a sign of good performance). Higher values
Queue to become (>100) indicate that Job Scheduler has a large
available or for an number of jobs queued for execution. This can be a
idle executor thread. symptom of one of the following:
A large number of jobs were created or recently
scheduled
The number of new jobs is too large for the
execution speed
Jobs are waiting due to a blocked Synchronization
Queue
The Job Scheduler service is hanging and halting
the job processing
Scheduler The number of The number of jobs loaded into the memory by Job
currently scheduled Scheduler waiting for their scheduled time to arrive.
scheduled jobs
jobs. The value of the counter depends on the configuration
and should be equal to the number of current jobs in
the system scheduled for future execution.
Machine Integrator
MI Action The average delay The time that passes between an action triggered for
Execution between the time execution and the actual execution start (that is, the
Delay that the action has time the action spends in the queue). This is for
been added to the asynchronously executed actions (Invoke Standard
executing queue Operation) (in milliseconds).
and the time that it
started to execute.
MI Action The average action The time the system needs to process a single action
Execution execution time. (in milliseconds).
Duration
MI Action The total number of The number of all the executed actions since the
Executions executed actions system was last restarted (both failed and successful
since the last restart. actions).
MI Action The number of The number of executed actions per second (failed
Executions / executed actions and successful).
sec per second.
MI Action Group The total number of The number of action executions triggered by
Triggers trigger action changes made to the MI Point values.
groups.
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 17

MI Action Group The number of The number of action executions triggered by

Triggers / sec trigger action groups changes made to the MI Point values per second.
per second.
MI Failed Action The total number of The number of actions that failed to be executed since
Executions failed executed the system was last restarted (total minus successful).
actions since the
last restart.
MI Failed Action The number of failed The number of actions that failed to be executed per
Executions / executed actions second (total minus successful).
sec per second.
MI Failed Point The total number of The number of failed attempts to read machine Points
Reads failed read Points triggered by MI (total minus successful).
since the last restart.
MI Failed Point The number of failed The number of failed attempts to read machine Points
Reads / sec read Points per triggered by MI per second (total minus successful).
second.
MI Failed Point The total number of The number of failed attempts to write Points to a
Writes failed write Points machine triggered by MI (total minus successful).
since the last restart.
MI Failed Point The number of failed The number of failed attempts to write Points to a
Writes / sec write Points per machine triggered by MI per second (total minus
second. successful).
MI Number of The average The number of simultaneous subscription queues
Subscription number of (being pairs of browser instances and inputs of the
Queues subscription “get value after change or from buffer” type) waiting to
queues. be processed by an operation.
MI Pending The number of The number of actions waiting for execution.
Actions currently pending
jobs.
MI Point Reads The total number of The number of attempts to read machine Points
read Points since triggered by MI (failed and successful).
the last restart.
MI Point The number of read The number of attempts to read machine Points
Reads / sec Points per second. triggered by MI per second (failed and successful).
MI Point Writes The total number of The number of attempts to write Points to a machine
write Points since triggered by MI (failed and successful).
the last restart.
MI Point Writes / The number of write The number of attempts to write Points to a machine
sec Points per second. triggered by MI per second (failed and successful).
MI Received The total number of The number of received Point value change
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 18

Point received Point information pieces from the machine.

Subscription subscriptions.
MI Received The number of The number of received Point value change
Point received Point information pieces from the machine per second.
Subscriptions / subscriptions per
sec second.
MI The average length The number of elements in a subscription queue.
Subscriptions of the subscriptions
Queue Length queue.
MI Successful The total number of The total number of successfully executed actions
Action successfully since the last restart (total minus failed).
Executions executed actions
since the last restart.
MI Successful The number of The number of successfully executed actions per
Action successfully second (total minus failed).
Executions / executed actions
sec per second.
MI Successful The total number of The number of successful attempts to read machine
Point Reads successfully read Points triggered by MI (total minus failed).
Points since the last
restart.
MI Successful The number of The number of successful attempts to read machine
Point Reads / successfully read Points triggered by MI per second (total minus failed).
sec Points per second.
MI Successful The total number of The number of successful attempts to write Points to a
Point Writes successfully written machine triggered by MI (total minus failed).
Points since the last
restart.
MI Successful The number of The number of successful attempts to write Points to a
Point Writes / successfully written machine triggered by MI per second (total minus
sec Points per second. failed).

4.2.2 Apriso JobExecutor Group

Job Executor Performance Counters are created per instance of Job Executor. They belong to
a separate group called Apriso Job Executor.

Counter Description Meaning

Executor Active The number The number of currently active threads used by Job Executor
Executor of active to execute jobs. The value is also equal to the number of
Threads (busy) currently executed jobs.
execution
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 19

threads. The maximum value is equal to the limit of the threads

defined in Central Configuration. It should stay below the
maximum limit the majority of the time. Lower values indicate
a good performance, and very low values (close to zero)
indicate that a small number of threads are currently being
used to execute the jobs. Higher values (close to the limit
defined in Central Configuration) indicate that most of the
available threads are busy and additional requests (new
jobs) may need to wait to be executed.
Executor Job The average The delay in the execution of a job compared to the creation
Execution delay time (or the job creating time for immediate jobs). The delay
Delay between the should be as small as possible. Lower values indicate good
time a job has performance and that Job Executor is starting job executions
been created correctly. Higher values (>1 sec) indicate that Job Executor
and the time it is delaying job executions as a result of performance issues.
was
published for
execution (in
milliseconds).
Executor Job The total time The time required to process a job in Job Executor. The
Execution of jobs duration of the job execution should be as short as possible.
Duration execution (in Lower values indicate better performance. Long durations
milliseconds). (>2 sec) mean performance issues in the system or the
existence of jobs that by design take a long time to execute.
Executor Job The number The overall number of processed jobs since the last restart
Executions of executed (both successful and failed jobs are shown). The value of the
jobs. counter should increase continuously. When the value does
not increase, this is an indication that jobs are not being
processed (as in, there is an issue in Job Executor) or jobs
are not being created.
The actual speed of the increase depends on the system
configuration, functionality, and load.
Executor Job The number The number of Executor Job Executions per second. A high
Executions / sec of jobs value indicates that more jobs are being executed and that
executed per system performance is good. Lower values mean that the
second. system is experiencing performance issues (e.g., the system
is fully loaded) or user inactivity. The actual numbers
depend on the system configuration, functionality, and load.
Executor Failed The number The overall number of failed jobs since the last restart. The
Job Executions of failed jobs. value should be as close to zero as possible and should not
grow. Lower values indicate good performance, while higher
values indicate that many jobs are failing during the
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 20

execution as a result of errors in processing.

The actual numbers depend on the system configuration,
functionality, and load.
Executor Failed The number Shows the number of failed job executions per second. Has
Job Executions of failed jobs the same meaning as the Executor Job Executions (failed)
/ sec per second. counter above.
Executor The number Shows the overall number of successful jobs since the last
Successful Job of restart. The value of this counter should increase
Executions successfully continuously. When it does not, one of the following is
executed occurring:
jobs. Jobs are not being processed (as in, there is an issue in
Job Executor)
Jobs are being processed but are failing
New jobs are not being created (as in, there is a small
load on the system)
The actual numbers depend on the system configuration,
functionality, and load.
Executor The number The number of successful job executions per second. Has
Successful Job of the same meaning as the Executor Job Executions
Executions / sec successfully (successful) counter above.
executed jobs
per second.
Executor new The number The number of new jobs created by DELMIA Apriso and
Jobs of new jobs discovered by Job Executor during the last load. The value
recently should reflect the number of new background jobs created
loaded by the by the system.
Job Executor
The actual numbers depend on the system configuration,
service.
functionality, and load.
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 21

5 Diagnostics
DELMIA Apriso is instrumented with diagnostic logging, the main purpose of which is to
persist the system behavior to storage so that it can be easily monitored and reviewed in case
an abnormal situation occurs. Every application in the DELMIA Apriso suite has code
implemented internally that logs information about the events that occur during execution.
Therefore, the administrative tasks focus on customizing the output of the logging. This means
that it is up to the administrator to decide on how to monitor and react to specific events. The
administrator can edit the DELMIA Apriso Logging configuration files to achieve the desired
effect.

5.1 Diagnostic Logging

DELMIA Apriso’s Logging subsystem is built upon the Log4Net class library (version 1.2.9),
which is a powerful logging framework for .NET applications. The class provides the runtime
logging ability without the need to perform binary modifications to the application. All the
official Log4Net documentation is valid for the DELMIA Apriso Logging library.
For more information about Logging in DELMIA Apriso, please refer to the Logging Technical
Guide.

5.2 Event Log

In order to diagnose different situations, looking into the Event Log (for details, see the
Logging Technical Guide) or the IIS logs (for details, see the Security Implementation Guide)
is recommended.
By default, DELMIA Apriso Logging is configured to log critical messages into the Windows
Event Log. The messages in this log are exactly the same as the ones logged in the
FatalErrorsLog.log file. Apart from the information supplied by DELMIA Apriso, the event log
messages have additional fields that are automatically populated by the operating system
computer “name,” “username,” and “EventID.” DELMIA Apriso creates its own folder in the
Windows Event Log to make the messages more accessible. For more information, please
refer to the Logging Technical Guide.

5.3 Response for Common Critical Actions

This section lists descriptions for the critical actions that need to be performed by the DELMIA
Apriso Administrators when specific system situations occur.

Event Log Rules and Actions List

Source FlexNetSchedulingService
Type An error.
Description Contains the phrase “FlexNet Job Scheduler service failed to execute a
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 22

Filter scheduled job.”

Description The FlexNet Job Scheduler service failed to execute a scheduled job:
Text JobId: {0}
JobName: {1}
ActionId: {2}
ActionName: {3}
ExecutionInfo: {4}
Administrative Use the Job Scheduler administration screen to find out details about the
Action failure and re-execute the job, if required.

Performance Monitor Rules and Actions List

Source Database Transactions Rolled Back / sec

Type >0.
Description The database transactions are not finished correctly. Due to errors in
Filter processing, the transactions are rolled back.
Description Consult the log files to find the reason for the failing transactions.
Text
Administrative Raise an alert to the Administrator.
Action
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 23

6 Deploying Service Packs

A Service Pack is a self-contained installation package that will deploy all the binaries through
an automated installation with minimal user input. It substitutes newer versions of files and
makes all the necessary modifications to the DELMIA Apriso configuration files (XML), leaving
few manual operations for the user to perform.
If a Service Pack contains literal translations (e.g., an export of the Localization Repository
database) or any manual operations are required, this will be described in the accompanying
“Readme” document.
After a DELMIA Apriso version is officially released, all the future updates are delivered only in
the Service Packs. Please note that it is also possible to create a custom enhancement for
DELMIA Apriso.

6.1 Assumptions
A Service Pack is an upgrade to the full product version. It must be performed as an upgrade –
with the master version present.
The Service Pack setup requires the same user rights (privileges) as the major DELMIA
Apriso application (Web) server: a user that is in the administrators group.

Before you start installing a Service Pack, you must assign the System Administrator
and Deployment Administrator Roles to the Employee.

Each Service Pack is cumulative, meaning that it contains all the previously released Service
Packs for the specific DELMIA Apriso version. If the user has version 2020 for example, it is
not necessary to install DELMIA Apriso 2020 Service Pack 1 before installing DELMIA Apriso
2020 Service Pack 2. When the user has Service Pack 1 already installed, Service Pack 2
may still be installed on it.

6.2 Service Pack Installation Process

In order to install a Service Pack read and follow the instructions given in the “Readme”
document that is delivered together with Service Pack.

6.3 Uninstallation
Each Service Pack uninstallation backs up the configuration files that were changed by the
given Service Pack. The backup made before uninstallation of the Service Pack is located in
the: <drive>\Program Files\Dassault Systemes\DELMIA Apriso
2020\HotFixes\<ServicePackVersion>\ConfigurationBackup\<DateTime>_Uninstall

During uninstallation, these files and folders are not removed.

DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 24

In order to revert DELMIA Apriso to a particular Service Pack version, the latest installed
Service Pack should be uninstalled from Windows (follow this path: Control Panel } Add or
Remove Programs/Programs and Features). During uninstallation, the configuration files
that were changed by the Service Pack will be rolled back automatically to their state before
the Service Pack was installed.
For example, if Service Pack 2 is installed over Service Pack 1 on DELMIA Apriso 2020:
Service Pack 1 and Service Pack 2 are installed in Windows
Uninstalling Service Pack 2 results in the following:
Service Pack 1 is still present in the system
The configuration files changed by Service Pack 2 are rolled back to their state before
the installation of Service Pack 2
The backup of the configuration files made during the uninstallation of Service Pack 2 is
available in the location written above

When the DELMIA Apriso setup is uninstalled, all the Service Packs installed for the
version are uninstalled automatically. However, uninstalling the Service Pack manually
is recommended for the proper removal of the files changed by these Service Packs.

6.4 Upgrading Client Computers

When a Service Pack is installed on the server, it replaces all the installation files that exist on
the server as well. This means that ClickOnce applications are updated and manifests are
regenerated.

6.5 Running Post-Upgrade Utility

The behavior of Post-Upgrade Utility is exactly the same as during the upgrade to a major
DELMIA Apriso version. For more information about Post-Upgrade Utility, refer to Post-
Upgrade Utility Help.

6.6 Installing in Silent Mode

Alternatively, the DELMIA Apriso Service Pack setup can be invoked in Silent Mode (that is,
without any user interaction). This setup is similar to the installation of the main version of
DELMIA Apriso. However, all the parameters which were used in the setup of the main
version are ignored, as they cannot be configured during the installation of the Service Pack.
To run a Basic MSI setup silently, type the following in the command line (this is an example):

“DELMIA Apriso 2020 SP1.exe” /s /v”/qb”

To uninstall silently, type the following in the command line:

“DELMIA Apriso 2020 SP1.exe” /s /x /v”/qb”

DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 25

6.7 Third-Party Service Pack Installation

Please note that the DELMIA Apriso Software License Agreement (SLA), which governs the
maintenance terms for DELMIA Apriso, requires that the third-party components on which
DELMIA Apriso depends be installed and upgraded to the patch and Service Pack levels
stated in the DELMIA Apriso product documentation (specifically, in this case, the DELMIA
Apriso Installation Guide and the Release Notes). Such a required patch is unique for nearly
each major or minor release of DELMIA Apriso. While DELMIA Apriso makes an extensive
effort to certify its releases on the stated third-party components, the new releases and patches
from them are only tested when absolutely necessary (see below) and on a much smaller
scale. It is therefore impossible for DELMIA Apriso to 100% warrant that the operation of
DELMIA Apriso will be uninterrupted or error-free, or that all the defects found can be
corrected or corrected within our normal service levels.
On the other hand, if a patch issued by a dependent third-party addresses a critical security,
stability, or performance defect, DELMIA Apriso’s policy is to take proactive measures to test
and recertify DELMIA Apriso on such newer patches. DELMIA Apriso will proactively notify
our customers of such dependencies and the associated DELMIA Apriso Service Packs
released in support of them (if any).
If, despite the aforementioned concerns, the customer proceeds and applies a more recent
patch than is supported, DELMIA Apriso will reasonably perform within the realms of the
standard maintenance agreement in order to diagnose and provide resolution to the issues
that are discovered. However, if DELMIA Apriso cannot provide resolution within a reasonable
and cost-effective time period, the only recourse may be to roll back to a supported service
level.
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 26

7 Upgrade to New Versions

The upgrade process for a new version of DELMIA Apriso consists of:
Server upgrade
Database upgrade

For more details about the DELMIA Apriso Database Upgrader and DELMIA Apriso
database upgrading, refer to the Database Upgrader Help

Functionality upgrade
For more information, refer to the DELMIA Apriso Installation Guide and DELMIA Apriso
Upgrade Guide.
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 27

8 Database Maintenance
DELMIA Apriso is a database system, and database performance is essential for performance
of the whole system. This guide does not cover all the instructions, as it only focuses on the
most important ones. Using common sense, the database vendor recommendations and, other
best practices is recommended.

8.1 Gathering Oracle Database Statistics

For deployments based on an Oracle Server, ensuring the refreshing of database statistics is
recommended. The database created using the Database Configuration Assistant GUI tool is
automatically configured to gather table and index statistics every day between 10:00 PM and
6:00 AM.
The frequency and hours of the statistics collection can be modified as needed using the
Enterprise Manager Database Control. The best practice is to keep the statistics up-to-date.
The job that gathers the statistics should run at least once a day, if possible. If there is no
default job, one can be created manually using the catmwin.sql script located in: ORACLE_
HOME\RDBMS\ADMIN.

Manually collecting the statistics can be done through the Enterprise Manager Database
Control or by using the built-in DBMS_STATS PL/SQL package.
The statistics for frequently changed tables should be collected in shorter intervals. This can
be done manually, or custom created scripts can be scheduled using the DBMS_
SCHEDULER package or the Enterprise Manager Database Control interface.

8.2 Archiving
The continuous monitoring of the database load is critical for maintaining an acceptable level
of system performance. During the normal running of the system, more and more data is
collected in the operational database. DELMIA Apriso Archiving is a tool that allows the user
to define and execute the process of operational database cleaning. The removed data may
be transferred to another database or deleted completely. The process of cleaning a database
may be scheduled to occur at specific intervals. The Administrator needs to ensure that a
database cleaning operation is performed on a regular basis. DELMIA Apriso Archiving can
be used with any version of DELMIA Apriso, but prepared configurations of DELMIA Apriso
Archiving are dependent on the version of the database.
For more information on DELMIA Apriso Archiving, refer to the Archiving Help.
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 28

Figure 3 DELMIA Apriso Archiving

8.3 Backup and Restore

Performing a backup action with the use of the best practices offered by an SQL Server
adapted to local IT policies is recommended. Please refer to the respective backup and
recovery guidelines provided by Microsoft and Oracle.
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 29

9 Miscellaneous/Troubleshooting
9.1 Modifying Session Timeout
Issue
DELMIA Apriso logs out the user too soon or lets the session last for too long.

Solution
Depending on the needs in a particular environment, it can be useful to modify the session
timeout to a desired value (or even disable it in the case of a text device).
The session timeout is set separately for the Portal and for Process Builder in DELMIA Apriso
Central Configuration (directly or using the DELMIA Apriso Configuration Manager). The key
names are PortalSessionTimeout and ProcessBuilderSessionTimeout, respectively. Disabling the
session timeout for text devices is done in the text client configuration using the
KeepSessionAlive key (for details, see Central Configuration Documentation)

The timeout settings also need to be changed and aligned in the Web Configuration
(the web.config file). For a detailed description of the session timeout configuration, refer
to the Security Implementation Guide.

9.2 Modifying Data Lifetime for Menu Data (Menu Items)

Issue
In the Portal, when creating a new user or assigning new privileges to an existing one, the
changes do not take effect immediately.

Solution
The Menu Data Lifetime is set in DELMIA Apriso Central Configuration. The key name is
MenuDataAbsoluteLifetime (for details, see Central Configuration Documentation).

It is recommended that this be set to greater than one hour (the default value of 3600
seconds), except during the test phase, during which menu changes need to be reflected
quickly.
For a detailed description of the Portal configuration, refer to the Portal Implementation Guide.

9.3 Access Rights to the Apriso Logging Folder

By default, the DEMIA Apriso logs are created in: <drive>\Temp\AprisoLogs.
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 30

Usually a Temp folder has full access rights set for everyone. If access to the Apriso logs
folder is restricted, an ASP.NET user must at least have the write permission. If not, DELMIA
Apriso can work without displaying warning messages, but no logs will be created.

9.4 Disabling Antivirus Scanning for Temporary Folder

Issue
Microsoft .NET runtime creates several temporary files in the Temp folder. Immediately after
creation, they are loaded into the memory and used. Some antivirus programs block these
files for virus scanning purposes, which prevents .NET runtime from loading them. As a result,
.NET runtime reports an error saying that those files with temporary names cannot be loaded.
The error looks similar to the following exception message (the assembly name is random and
different each time): “File or assembly name zqconzy0.dll, or one of its dependencies, was not
found.”

Solution
To eliminate this issue, disable the antivirus scanning for the folder used by .NET runtime to
create the temporary files. The folder name is stored in the TMP environment variable of the
account used by .NET runtime. To find the folder’s name, analyze the environment variable
values for the account used to run the .NET application.
The default location of the Temp folder (configured by the value of the TMP environment
variable) is: C:\Windows\Temp.
The antivirus scanning of this folder should be disabled when the above error messages are
reported.
The same issue can occur on client machines when using M&M screens. In such a case, virus
scanning on the local machine should be disabled by following the same procedure as above.

9.5 Setting the Optimizer Mode for the DELMIA Apriso

Database
When using Oracle as a DBMS, it is strongly recommended to use COST as a valid Optimizer
Mode option. This option is also used when a default CHOSE is selected. The RULE option is
old (as in, obsolete) and it is to be removed in future versions of Oracle.

9.6 Connectivity Problems Due to Proxy Configuration

DELMIA Apriso does not support or recommend using a proxy server in the network
configuration.
In some proxy configurations (e.g., for Squid), POST messages will not get through. The
application will also display a connectivity error message straight away. In most cases, the
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 31

proxy is set explicitly in the browser configuration. However, wide open networks use a
transparent proxy/cache service, which intercepts all traffic (that is, filtering, caching, and
policy enforcements). Such a proxy cannot be disabled on the client side, and thus all traffic is
forced to move through it.
In this case, make sure the HTTP 1.1 standards are used, as this allows for a wiser distribution
of network traffic (for details, refer to World Wide Web Consortium article related to Header
Field Definitions). However, this also does not guarantee correct connectivity. Please consult
DELMIA Apriso Support for details.
The section below describes how to omit the proxy for a DELMIA Apriso server.

Adding a DELMIA Apriso Server to the Proxy Configuration Exceptions List

This action is a workaround wherein if the client machine has a proxy configuration set in a
browser, then the ClickOnce installation does not work. To add a server machine to the Proxy
Exceptions list, perform the following steps (as presented in Figure 4 Adding a DELMIA Apriso
server to the Proxy Settings Exceptions list):
1. Open Internet Options.
2. Go to the Connections tab and click LAN settings.
3. In the Proxy server group, click Advanced.
4. In the Proxy Settings window that appears, add the name of the server you are using in
the Exceptions box.
5. Accept your changes.
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 32

Figure 4 Adding a DELMIA Apriso server to the Proxy Settings Exceptions list

9.7 ClickOnce Applications Failing to Start when Root

Certificates are Missing
Because DELMIA Apriso uses root certificates for security purposes (see Other Prerequisites
and Configurations to be done before the Installation section of the DELMIA Apriso Installation
Guide), it is required to keep them up-to-date.
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 33

Issue
If the Update Root Certificate feature of the Windows server cannot automatically retrieve or
update the root certificates, the required root certificate is not available on the system and the
DELMIA Apriso ClickOnce applications will not work.
These are the possible reasons that the system may not have the updated root certificates:
Lack of an Internet connection or lack of access to the required Microsoft URL
The update is manually excluded from the list of optional ones
A company Group Policy disabled this feature

Solution
Microsoft extensively describes this issue in the KB931125 article at Microsoft Support.
This article contains information about different kinds of Windows update root certificates and
also contains a download link to a list of the third-party certification authorities (CAs) that are
trusted by Microsoft and whose root certificates are distributed through the Microsoft Root
Certificate Program.
The required root certificates should be downloaded and installed to meet the DELMIA Apriso
requirement according to the above Microsoft article.

9.8 Session Sharing

The browser may store session information from its multiple instances (that is, new windows
and tabs, duplicate tabs) in the same location. This can cause problems when logging in to
DELMIA Apriso more than once from the same machine at the same time.

Bear in mind that logging in to DELMIA Apriso on multiple tabs is not recommended.

9.9 Running Apriso Services Using a Domain Account

Issue
If Apriso services are required to run using a domain account, then certain conditions must be
met. Otherwise, the following error will occur when starting an Apriso service:
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 34

Service cannot be started. System.ServiceModel.AddressAccessDeniedException: HTTP could not

register URL http://+:32608/stateservice/mex/. Your process does not have access rights to
this namespace (see http://go.microsoft.com/fwlink/?LinkId=70353 for details). --->
System.Net.HttpListenerException: Access is denied
at System.Net.HttpListener.AddAll()
at System.Net.HttpListener.Start()
at System.ServiceModel.Channels.SharedHttpTransportManager.OnOpen()
--- End of inner exception stack trace ---
at System.ServiceModel.Channels.SharedHttpTransportManager.OnOpen()
at System.ServiceModel.Channels.TransportManager.Open(TransportChannelListener
channelListener)
at System.ServiceModel.Channels.TransportManagerContainer.Open
(SelectTransportManagersCallback selectTransportManagerCallback)
at System.ServiceModel.Channels.HttpChannelListener.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Dispatcher.ChannelDispatcher.OnOpen(TimeSp...

Solution
In order for Apriso services to work correctly when using a domain account, one of the
following conditions must be met:
The user account used to run the service must be a part of the Administrators group on a
local machine, or
The administrator needs to run following command for each service and its corresponding
port:
netsh http add urlacl url=http://+:32608/stateservice/mex/ user=Domain\UserName

This example is for StateService. The addresses and ports that need to be registered are
different for each service, and they can be found in the RemotingServices.config configuration
file located in each service installation folder.

9.10 Avoiding Issues Concerning the UTC Function in Oracle

As a best practice, the default session time zone should be set using the ORA_SDTZ
environment variable on the application server (that is, the machine where DELMIA Apriso is
installed). It should be set to one of the values selected from the V$TIMEZONE_NAMES
dynamic performance view (e.g., for an application server located in Poland, it could be set to
the Poland or CET value). The time zone value of the current session can be returned by the
following statement: SELECT SESSIONTIMEZONE FROM DUAL.
When checking the time zone value, it should be taken into consideration that different tools
can get information from different locations. .NET applications get the time zone value from the
ORA_SDTZ environment variable; Java applications get the value from Control Panel
}Regional and Language settings; and other applications can check the registry.
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 35

Although the ORA_SDTZ value is not necessary for DELMIA Apriso to work correctly, it helps
avoid the issues introduced by custom solutions.

9.11 DELMIA Apriso Portal Display Issue When Using

HTTPS
Issue
If the “ERR_SSL_FALLBACK_BEYOND_MINIMUM_VERSION” error occurs in the browser, it
may suggest that the website attempts to establish a secure connection using a protocol
standard which is lower than acceptable.

Solution
Under current settings, the server may be unable to provide a protocol higher than TLS 1.0. In
this situation, TLS 1.2 should be first set as active. If this fails to fix the problem, enable TLS
1.1. Should the issue persist despite these efforts, set TLS 1.0 as the active protocol for SSL.
DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 36

10 References
Internal Documentation
1. DELMIA Apriso Upgrade Guide
A guide to the upgrade process of the DELMIA Apriso solution. It covers the most common
scenarios and discusses known issues and configurations in detail. Please note that this
document is only available from the 3DS Support.
2. Apriso Classic Portal Help
This help describes use of the Apriso Classic Portal, its configuration, and its
administration. To access it, click Help while on the Portal Home page, or navigate to the
Help via the DELMIA Apriso Start Page.
3. Logging Technical Guide
Describes the DELMIA Apriso Logging subsystem and provides information on managing
and customizing it. This guide gathers all the information required by a System
Administrator to effectively use DELMIA Apriso Logging so that it meets the needs of every
system on which it is deployed.
4. Archiving Help
Provides information on using DELMIA Apriso Archiving, which allows users responsible
for archiving custom databases to create their own Archiving procedures on the basis of the
described tools and examples.
5. Database Upgrader Help
Provides the background information necessary to use the DELMIA Apriso Database
Upgrader (DBU) tool and describes how to carry out common tasks.
6. Security Implementation Guide
Provides an overview of DELMIA Apriso security and information on effectively securing all
instances of DELMIA Apriso.
7. Portal Implementation Guide
Provides an overview of the DELMIA Apriso Portal and the Apriso Classic Portal along with
the background information on understanding their roles, capabilities, and customization.
8. DELMIA Apriso Installation Guide
Describes the installation of the DELMIA Apriso solution. The guide covers the software
and hardware requirements as well as the installation procedure.

All the internal documents referenced in this section are available from the DELMIA Apriso
Start page, which can be accessed on your DELMIA Apriso server (<server name>/apriso/start).
The newest versions of all documents are available from 3DS Support at:
https://www.3ds.com/support/documentation/
 DELMIA Apriso | DELMIA Apriso 2020 Administration Guide 37

9. Process Builder Help

Provides an overview of DELMIA Apriso Process Builder (PB) and information on installing
and using the application. This Help describes the user interface elements, entity
maintenance, available Business Controls, and management of Processes, Operations,
and Screen Flows.
10. Business Integrator – Configuration Guidelines Technical Guide
Provides the information required to configure DELMIA Apriso Business Integrator (BI),
which enables adjusting the standard DELMIA Apriso configuration (installed) to custom
configuration requirements.
11. Post-Upgrade Utility Help
Provides an overview of DELMIA Apriso Post-Upgrade Utility (PUU), presents the
background information on using it, and describes how to carry out common tasks. This
Help is intended for users who administer and train on performing basic everyday
procedures with the use of Post-Upgrade Utility.
12. Configuration Manager Help
Provides the background information necessary to use the DELMIA Apriso Configuration
Manager tool and describes how to carry out common tasks.
13. Central Configuration Documentation
Describes in detail all the keys of the Central Configuration (CC) file for DELMIA Apriso.
Various sections group the keys for individual modules or distinct functional areas.

3DS Support Knowledge Base

If you have any additional questions or doubts not addressed in our documentation, feel free to
visit the 3DS Support Knowledge Base at https://support.3ds.com/knowledge-base/.

All the internal documents referenced in this section are available from the DELMIA Apriso
Start page, which can be accessed on your DELMIA Apriso server (<server name>/apriso/start).
The newest versions of all documents are available from 3DS Support at:
https://www.3ds.com/support/documentation/