The management interfaces in Wildfly are secured by default to prevent security violation from remote systems. Local non-HTTP access is protected by a SASL mechanism which consists of a negotiation between the client and the server when the client connects for the first time from the localhost. To access the Wildfly administration console, you must register an Administrator user as follows:

Open a command prompt in the <JBOSS_HOME>/bin directory. Enter ./add-user[.sh|.bat] <username> <password> <ManagementRealm>

After configuring Wildfly administrator user restart the application server. Verify by logon to Wildfly management Console with admin user.

http://(IP Address):9990

System will redirect user to the Wildfly admin console on successful logon.

The tasks you perform to complete the installation are listed in the following section. The section also gives a summary of each task and explains if the task is required or optional, along with links to sections that describe the task in more detail.

You can install ONEWEB as an administrative user (root) or as a non-administrative user (non-root) and later you must use the same user to install the required software. For example, you must install ONEWEB, Java and WebSphere Application Server using the same user.

Administrator user - If you want the administrator user (root) to install products on a computer, please make sure the files have all privilege to execute.

Non-administrator user - If you want a specific user to install products on a computer, please make sure the user has all the privileges on directory. If you want a group of users to install products on a computer, please make sure the group has all privileges on directory using the group mode. You can install ONEWEB by using one account and offerings by using another account that is in the same group.

To configure ONEWEB database you must follow the below steps.

Step1: Create Schema & role authorization. Use following details to create database schema on postgresql server. Create schema for ONEWEB Application by using SQL script. Execute: create_schema.sql Create role authorization for ONEWEB Application by using SQL script. Execute: create_role.sql Alter password to user role by using SQL script. Execute: alter_password.sql

Step2: Restricting database user permissions. Alter administrator's privilege and search_path on schema for each user. Alter privilege for ONEWEB Application by using SQL script. Execute: alter_priviledge.sql

Step3: Create table and initial data.

Reference: https://www.postgresql.org/docs/9.3/tutorial-install.html

To plan your database configuration, you need to know which databases must be configured to use the software. You also need to know the following like which components of ONEWEB you will use and their associated databases, the tasks required for administering the databases, and the security privileges associated with the database system.

Database creation is the mandatory first step so that you can connect the data source when you deploy the ONEWEB archives.

Below is the list of database schemas and their associated component name in ONEWEB.

Recommendation

Separate table spaces for each application This makes sure that the issues with one table space do not impact the second application. Table space can be taken offline without impacting all applications instead of the one that has data files in it.

Table and indexes must be maintained in separate table spaces This is a typical implementation in production systems.

Properly name data files that are part of table space Easily readable convention EAF_MASTER_data_01.datafile , BPM_data01.datafile

A web server is responsible for accepting HTTP requests from clients (web browsers) and serving them HTTP responses along with optional data content, such as web pages (HTML documents) and linked objects such as images. ONEWEB supports both Apache Web as well as IBM HTTP server.

To configure Apache2 you must follow below steps.

Setting Apache reverse proxy. Configure a new virtual host or site, copy that file into the same directory

Disable and Enable the new VirtualHost using the a2dissite, a2ensite utility and restart Apache2

Disable

Enable

Restart

Apache2 Modules. Use the a2enmod utility to enable a module:

sudo a2enmod proxy
sudo a2enmod proxy_http
sudo a2enmod proxy_ajp
sudo a2enmod rewrite
sudo a2enmod deflate
sudo a2enmod headers
sudo a2enmod proxy_balancer
sudo a2enmod proxy_connect
sudo a2enmod proxy_html

Setting port. Change Apache default port to a custom port. Edit: port.conf

Testing your application's context root.

An application server is a software framework that provides both facilities to create web applications and an environment to run them. ONEWEB supports the following Application Servers

• Websphere Application Server

• JBOSS EAP

• Wildfly

This section includes the step by step preparation procedure to install ONEWEB on the application server.

To use ONEWEB on a new instance of Wildfly 10.0.0.Final, you must establish your database, deploy the provided archives for this server, and perform a number of configuration tasks. You can use one of two operating modes: stand-alone server or managed domain. As a stand-alone server, the operating mode is similar to the previous versions of Wildfly.

ONEWEB requires a full profile. A sample full profile is provided for both stand-alone and domain modes.

The Wildfly Management Console and Management CLI interfaces allow administrators to manage application deployments in a production environment.

To configure ONEWEB on Wildfly you must follow a series of steps:

The first step concerns your choice of persistence and permissions on the database. Create a database for ONEWEB before the deployment of the WAR file. You should create the database schema using the SQL scripts following the details in

Connection to the ONEWEB database, as shown in the data source credentials and any subsequent requests to the database are handled through a database user. This database user is for example erp_oneweb.

Refer to section Install ONEWEB Application Components for the detailed step by step information on how to deploy ONEWEB.

This document provides access to the detailed system requirements information on the supported releases of ONEWEB.

The following table shows the detailed system requirements information for the specified release and operating system for ONEWEB.

Operating System

AIX

Windows

Linux

Application Server Prerequisites

Databases Prerequisites

Java

Web Browsers

In this section we will detail the step by step process of installing the ONEWEB Application Components. You can deploy ONEWEB Application Components using the Wildfly Management Console or the Management CLI. This example illustrates using the Management Console.

This section provides step by step process of installing the ONEWEB Process Components. You can either deploy ONEWEB Components using the Wildfly Management Console or the Management CLI. This example illustrates using the Management Console.

The following table gives the datasource connection details for the ONEWEB database.

You can configure the data source by using the JBoss Management Console or the Management CLI. Here, you use the Management Console.

Log in to the JBoss Management Console. By default, http://(IP Address):9990 Navigate to the Datasources panel. Configuration -> Subsystems -> Datasources Select Type "Non-XA" -> and then click add (5) Create datasource -> Choose datasource "custom" and then click "Next"(7)

Specify the details for the new data source. Datasource Attribute Name: Datasource Name JNDI Name: Specifies the JNDI name for the datasource

JDBC Driver Select Detected Driver "postgresql.jar" and then click "Next"

Verify the datasource connection, click "Test Connection" and then click "Finish"

If you use data source persistence, you must install a driver before creating the data source. Use the below details to install database driver.

Download the JDBC driver from your database vendor. (ex. postgresql.jar)

Add the driver to Wildfly, using Wildfly Management console.

• Click on " Deployments" -> " Add" and select "postgresql.jar", click "Next"

• Check ✔ on Enable and Click "Finish"

The database driver is installed successfully.

This document will guide on how to enable single sign-on to access different applications deployed into different servers, where these applications belong to the same security domain.

Before you begin You need to have configured security domain which handles authentication and authorization. Verify the application EAR, WAR have use same security-domain

To enable SSO Turn on SSO in Wildfly server configuration Edit the standalone.xml as follows

/{WILDFLY_HOME}/standalone/configuration/standalone.xml.

The org.apache.catalina org.apache.catalina.connector property was used to set UTF-8 encoding in the Wildfly 10 configuration. These properties have no impact since Wildfly now uses Undertow. In order to set UTF-8 encoding instead of changing:

<system-properties>
<property name="org.apache.catalina.connector.URI_ENCODING" value="UTF-8" />
<property name="org.apache.catalina.connector.USE_BODY_ENCODING_FOR_QUERY_STRING" value="true" />
</system-properties>

Editing the standalone.xml as follows

/{WILDFLY_HOME}/standalone/configuration/standalone.xml

Add: system-properties tag

Edit: servlet-container

<servlet-container name="default">

Before you Begin To integrate ONEWEB application with the Wildfly authentication, you must register an Application user. Refer to section Step2: Configure access to Wildfly Management Console. You should select type to add user for Application user (b)

Authentication with Wildfly - Edit the standalone.xml as follows

/{WILDFLY_HOME}/standalone/configuration/standalone.xml

Add: <login-module> tag

Edit the standalone.xml as follows

/{WILDFLY_HOME}/standalone/configuration/standalone.xml

Before you configure you should have informed LDAP for configuration authentication with Wildfly Refer to section LDAP Integration

Example:

Add: <login-module> tag

Edit: value ldap setting

Wildfly use Subsystem configurations. A subsystem is an added set of capabilities added to the core server by an extension. A subsystem provides servlet handling capabilities a sub system provides and EE, EJB, IO etc. A profile is a named list of subsystems, along with the details of each subsystem's configuration EE Subsystem The EE subsystem allows you to configure common functionality in the Java EE platform, such as defining global modules, enabling descriptor-based property replacement, and configuring default bindings. managed executor service context-service The name of the context service to be used by the executor. core-threads The minimum number of threads to be used by the executor. If left undefined the default core-size is calculated based on the number of processors. A value of zero is not advised and in some cases invalid. See the queue-length attribute for details on how this value is used to determine the queuing strategy. hung-task-threshold The runtime, in milliseconds, for tasks to be considered hung by the managed executor service. If value is 0 tasks are never considered hung. jndi-name The JNDI Name to lookup the managed executor service. keepalive-time When the number of threads is greater than the core, this is the maximum time, in milliseconds, that excess idle threads will wait for new tasks before terminating. long-running-tasks Flag which hints the duration of tasks executed by the executor. max-threads The maximum number of threads to be used by the executor. If left undefined the value from core-size will be used. This value is ignored if an unbounded queue is used (only core-threads will be used in that case). queue-length The executors task queue capacity. A length of 0 means direct hand-off and possible rejection will occur. An undefined length (the default), or Integer.MAX_VALUE, indicates that an unbounded queue should be used. All other values specify an exact queue size. If an unbounded queue or direct hand-off is used, a core-threads value greater than zero is required. reject-policy The policy to be applied to aborted tasks. thread-factory The name of the thread factory to be used by the executor. IO Subsystem The IO subsystem allows you to define workers and buffer pools to be used by other subsystems. worker io-threads Specify the number of I/O threads to create for the worker. If not specified, a default will be chosen, which is calculated by cpuCount * 2 stack-size The stack size (in bytes) to attempt to use for worker threads. task-keepalive Specify the number of milliseconds to keep non-core task threads alive. task-max-threads Specify the maximum number of threads for the worker task thread pool.If not set, default value used which is calculated by formula cpuCount * 16 buffer-pool buffer-size The size of each buffer slice in bytes, if not set optimal value is calculated based on available RAM resources in your system. buffers-per-slice How many buffers per slice, if not set optimal value is calculated based on available RAM resources in your system. direct-buffers Does the buffer pool use direct buffers, some platforms don't support direct buffers Processor Core A processor core (or simply “core”) is an individual processor within a CPU. Many computers today have multi-core processors, meaning the CPU contains more than one core.

For many years, computer CPUs only had a single core. In the early 2000s, as processor clock speeds began plateauing, CPU manufacturers needed to find other ways to increase processing performance. Initially, they achieved this by putting multiple processors in high-end computers. While this was effective, it added significant cost to the computers and the multiprocessing performance was limited by the bus speed between the CPUs. By combining processors on a single chip, CPU manufactures were able to increase performance more efficiently at a lower cost. The individual processing units became known as “cores” rather than processors. In the mid-2000s, dual-core and quad-core CPUs began replacing multi-processor configurations. While initially only high-end computers contained multiple cores, today nearly all PCs have multi-core processors.

Thread The threads of a computer program allow the program to execute sequential actions or many actions at once. Each thread in a program identifies a process that runs when the program asks it to. Threads are typically given a certain priority, meaning some threads take precedence over others. Once the CPU is finished processing one thread, it can run the next thread waiting in line. However, it's not like the thread has to wait in line at the checkout counter at Target the Saturday before Christmas. Threads seldom have to wait more than a few milliseconds before they run. Computer programs that implement "multi-threading" can execute multiple threads at once. Most modern operating systems support multi-threading at the system level, meaning when one program tries to take up all your CPU resources, you can still switch to other programs and force the CPU-hogging program to share the processor a little bit. The term "thread" can also refer to a series of related postings in an online discussion. Web-based bulletin boards are made up of many topics, or threads. The replies posted in response to the original posting are all part of the same thread. In e-mail, a thread can refer to a series of replies back and forth pertaining a certain message. JVM Options there are three types of options that you can include to your JVM, standard, non-standard, and advanced options. If you try an advanced option, you always use the option with -XX . Similarly, if you’re applying a non-standard option, you use -X . Standard options don’t prepend anything to the option. Java heap size

-Xms - set initial Java heap size -Xmx - set maximum Java heap size -Xss - set java thread stack size

Xms – This option is to define starting heap size for JVM, e.g.,Xms2048m which means an initial heap size of JVM is 2 GB around. So, when a JVM starts, the heap memory will be this much big. Surprisingly yes! This is carried to prevent resizing during startup and enhance the startup time of JVM. Xmx – This option is to define the maximum heap size of JVM, e.g.,Xmx2048m which means the maximum heap size of JVM will be 2 GB only. You will essentially always have-Xms and -Xmx together. PermGen Size Earlier JVM options define the size of heap memory but -XX:PermSize is to define the size of PermGen space, where the string pool and class metadata is saved. This option is particularly effective for a web server like Tomcat, which often loads classes of the web application during deployment. By the way, It’s worth realizing that PermGen space is taken over by Metaspace in Java 8, and this option is not applicable if you are running with JRE 8 JVM. Handling ‘OutOfMemory’ Error To trigger heap dump on out of memory, you can use -XX:+HeapDumpOnOutOfMemoryError This JVM option produces a stack dump when your JVM dies with OutOfMemory Error. There is no expense involved unless an OOM really occurs. This flag is a requisite for production systems as it is usually the only way to determine the problem deeply.

The heap dump will be set up in the “current directory” of the JVM by default. If you wish to create heap dumps on specific directory, then run

-XX:HeapDumpPath= [path-to-heap-dump-directory] -XX:+UseGCOverheadLimit -XX:OnOutOfMemoryError="< cmd args >;< cmd args >"

The heap dump file can be huge in size, up to gigabytes, so assure that the target file system allows sufficient capacity. If we want to restart the server immediately after out of memory occur, then we can set this parameter of the same purpose –XX:OnOutOfMemoryError="shutdown -r" Trace class loading and unloading -XX:+TraceClassLoading and -XX:+TraceClassUnloading are two JVM options that we use to print logging information whenever classes loads into JVM or unload from JVM. These JVM flags are useful if you have any type of memory leakage linked to classloader and suspecting to it that classes are not unloading or garbage collected.

Recommended Standard Configure for ONEWEB:

Log in to the Wildfly Management Console (By default, http://(IP Address):9990)

Navigate to the Deployment panel (Highlighted as 1 in below figure). Click on Add (2)

Select "Upload new deployment" and then click Next (4)

Choose the Application WAR file. (Package name: "ONEWEB.AD.x.x.x.x.YYMMDD24HHMM.wildfly.war") and then click Next.

Select Enable and then click "Finish"

Wait for the confirmation message to be shown. The Application package has been deployed successfully.

Verify application with URL: http://(IP Application server):(port)/EAFUIWeb

Log in to the Wildfly Management Console. (By default, http://(IP Address):9990)

Navigate to the Deployment panel (Highlighted as 1 in below figure). Click on Add (2)

Select "Upload new deployment" and then click Next (4)

Choose the Application WAR file. (Package name: "ONEWEB.PGR.x.x.x.x.YYMMDD24HHMM.wildfly.war") and then click Next.

Select Enable and then click "Finish"

Wait for the confirmation message to be shown. The Application package has been deployed successfully.

Log in to the Wildfly Management Console. (By default, http://(IP Address):9990)

Navigate to the Deployment panel (Highlighted as 1 in below figure). Click on Add (2)

Select "Upload new deployment" and then click Next (4)

Choose the Application WAR file. (Package name: "ONEWEB.PGD.x.x.x.x.YYMMDD24HHMM.wildfly.war") and then click Next.

Select Enable and then click "Finish"

Wait for the confirmation message to be shown. The Application package has been deployed successfully.

Open ONEWEB Page Designer console by typing URL http://<ip>:<port>/PageDesigner/#/settings/db/migration

Click "Install"

Install page application. Application will respond with "Validated"

The Application package has been deployed and initialized successfully.

Verify application with URL: http://(IP Application server):(port)/PageDesigner

Before you start you need to configure the following data in database.

Log in to the Wildfly Management Console. (By default, http://(IP Address):9990)

Navigate to the Deployment panel (Highlighted as 1 in below figure). Click on Add (2)

Select "Upload new deployment" and then click Next (4)

Choose the Application EAR file. (Package name: "ONEWEB.AR.x.x.x.x.YYMMDD24HHMM.wildfly.ear") and then click Next.

Select Enable and then click "Finish"

Wait for the confirmation message to be shown. The Application package has been deployed successfully.

Verify application with URL: http://(IP Application server):(port)/FrontWeb

Before you start you need to configure the following data in database.

Log in to the Wildfly Management Console (By default, http://(IP Address):9990 )

Navigate to the Deployment panel (Highlighted as 1 in below figure). Click on Add (2)

Select "Upload new deployment" and then click Next (4)

Choose the Application WAR file. (Package name: "ONEWEB.PR.x.x.x.x.YYMMDD24HHMM.wildfly.war") and then click Next.

Select Enable and then click "Finish"

Wait for the confirmation message to be shown. The Application package has been deployed successfully.

Verify application with URL: http://(IP Application server):(port)/BPMREST

Before you start you need to configure the following data in database.

Log in to the Wildfly Management Console (By default, http://(IP Address):9990 )

Navigate to the Deployment panel (Highlighted as 1 in below figure). Click on Add (2)

Select "Upload new deployment" and then click Next (4)

Choose the Application WAR file. (Package name: "ONEWEB.PD.x.x.x.x.YYMMDD24HHMM.wildfly.war") and then click Next.

Select Enable and then click "Finish"

Wait for the confirmation message to be shown. The Application package has been deployed successfully.

Verify application with URL: http://(IP Application server):(port)/PD

This chapter will tell you how to verify all the components of the ONEWEB platform once all the components are installed. If any of the components are not installed properly then the verification procedure might fail.

This section provides step by step process of installing the ONEWEB Integration Components. You can deploy ONEWEB Components using the Wildfly Management Console or the Management CLI. This example illustrates using the Management Console.

Before you start you need to configure the following data in database.

Log in to the Wildfly Management Console (By default, http://(IP Address):9990 )

Navigate to the Deployment panel (Highlighted as 1 in below figure). Click on Add (2)

Select "Upload new deployment" and then click Next (4)

Choose the Application WAR file. (Package name: "ONEWEB.MFD.x.x.x.x.YYMMDD24HHMM.wildfly.war") and then click Next.

Select Enable and then click "Finish"

Wait for the confirmation message to be shown. The Application package has been deployed successfully.

Verify application with URL: http://(IP Application server):(port)/MicroFlow

Once the ONEWEB Platform is installed, you can verify the application by the following details.

App Designer

Login to the application with URL: http://(IP Application server):(port)/FrontWeb

Locate to App Designer -> Import Entity

Import Entity: EN_v001.entity.cfg.json

Go to App Designer >> Menu Configuration >> Create New Menu under APP Zone

ONEWEB Application Archive Package for IAM Feature is shown below.

Before you start you need to configure the following data in database.

Log in to the Wildfly Management Console (By default, http://(IP Address):9990 )

Navigate to the Deployment panel (Highlighted as 1 in below figure). Click on Add (2)

Select "Upload new deployment" and then click Next (4)

1. oose the Application WAR file. (Package name: "IAM2RESTService.x.x.x.x.YYMMDD24HHMM.wildfly.war") and then click Next.

2. Select Enable and then click "Finish"

3. Once successfully deployed, deploy the other packages as well.

Wait for the confirmation message to be shown. The Application package has been deployed successfully.

Verify application with URL: http://(IP Application server):(port)/IAM2Web

Before you start you need to configure the following data in database.

Log in to the Wildfly Management Console (By default, http://(IP Address):9990 )

Navigate to the Deployment panel (Highlighted as 1 in below figure). Click on Add (2)

Select "Upload new deployment" and then click Next (4)

Choose the Application WAR file. (Package name: "ONEWEB.MFR.x.x.x.x.YYMMDD24HHMM.wildfly.war") and then click Next.

Select Enable and then click "Finish"

Wait for the confirmation message to be shown. The Application package has been deployed successfully.

Verify application with URL: http://(IP Application server):(port)/MicroFlowRest

Once ONEWEB Process is installed successfully, you can verify the application with following detail.

Process Designer

Login to the application with URL: http://(IP Application server):(port)/FrontWeb

Navigate to Process Designer -> Create blank Project

Create New Process Name: Occurrence Management

Import File: Occurrence Management

Go to design tool

Once ONEWEB Application is installed successfully, you can verify the application with following detail.

MicroFlow Designer

Login to the application with URL: http://(IP Application server):(port)/FrontWeb

Navigate to MicroFlow -> Create blank Project

Create New Process with Name: XXX Service

Go to "Import"

Choose file getCurrencyFixer and Click "Import"

Once import is complete, go to Design tool and you can see the getCurrencyFixer Service