<commit_before>[id='apb-deploy-proc']
= Deploying a {PRODUCT} environment using the Automation Broker

To deploy a {PRODUCT} environment using the Automation Broker, you must find the Ansible Playbook in the OpenShift catalog, run it, and set the parameters as required. 

.Procedure

. In the OpenShift Web UI, select *Add to Project -> Browse Catalog*.

. In the search field, type *{PRODUCT}*.

. Select the *{PRODUCT} {PRODUCT_VERSION} APB* catalog entry.

. Click *Next*.

. Select the required architecture elements, as described on the screen, and click the *Next* button.
+
IMPORTANT: If you want to deploy an environment with immutable servers and a monitoring infrastructure, you must first install the *Immutable Server - Monitor* option and then the *Immutable Server - KIE Process Server* option.

. Enter the parameters as described on the screen. In most cases, the default values lead to a working deployment; you can modify them as necessary. You must enter the following settings:
+
** For the *Immutable Server - Monitor* option:
+
*** The *Maven repository URL* field. You must provide a Maven repository with the same versions of all the artifacts that are deployed on any monitored immutable servers.
*** The *Admin password* field. You must record the administrative user name and password to configure monitored servers to connect to {CENTRAL} Monitoring.
+
** For the *Immutable Server - KIE Process Server* option:
*** The *KIE Server Container Deployment*, *Git Repository URL*, and *Git Repository Reference* fields. These settings determine the source code that the deployment process builds and deploys on the {KIE_SERVER}.
*** If you deployed the *Immutable Server - Monitor* option and want to connect the server to the monitoring infrastructure:
**** Under *Router integration*, the service name of the `rhpam-immutable-mon-smartrouter` service.
**** Under *Controller integration*, the service name of the `rhpam-immutable-mon-rhpamcentrmon` service and the admin username and password that you set in the *Immutable Server - KIE Process Server* option.
+
[IMPORTANT]
====
Avoid each of the following combinations of settings. These combinations produce an invalid environment.

* *Process server*>**Database type** `H2` and *Process server*>**Number of replicas** exceeding `1`.
* *Process server*>**Database type** `External` and *Process server*>**Sets of Process Servers** exceeding `1`.
* *Red Hat - Single Sign-On* configured and  *Process server*>**Sets of Process Servers** exceeding `1`.
====
+
. Click *Next* to commence deployment.
+
After deploying the environment, you can access it using the HTTPS routes displayed in the OpenShift Web console. HTTP requests are redirected to HTTPS.

IMPORTANT: After deploying the service, you can scale the {KIE_SERVER} pods up and down as necessary. Do not scale the database pods.<commit_msg>external db for apb (#39) (#1446)<commit_after>[id='apb-deploy-proc']
= Deploying a {PRODUCT} environment using the Automation Broker

To deploy a {PRODUCT} environment using the Automation Broker, you must find the Ansible Playbook in the OpenShift catalog, run it, and set the parameters as required. 

.Procedure

. In the OpenShift Web UI, select *Add to Project -> Browse Catalog*.

. In the search field, type *{PRODUCT}*.

. Select the *{PRODUCT} {PRODUCT_VERSION} APB* catalog entry.

. Click *Next*.

. Select the required architecture elements, as described on the screen, and click the *Next* button.
+
IMPORTANT: If you want to deploy an environment with immutable servers and a monitoring infrastructure, you must first install the *Immutable Server - Monitor* option and then the *Immutable Server - KIE Process Server* option.

. Enter the parameters as described on the screen. In most cases, the default values lead to a working deployment; you can modify them as necessary. You must enter the following settings:
+
** For the *Immutable Server - Monitor* option:
+
*** The *Maven repository URL* field. You must provide a Maven repository with the same versions of all the artifacts that are deployed on any monitored immutable servers.
*** The *Admin password* field. You must record the administrative user name and password to configure monitored servers to connect to {CENTRAL} Monitoring.
+
** For the *Immutable Server - KIE Process Server* option:
*** The *KIE Server Container Deployment*, *Git Repository URL*, and *Git Repository Reference* fields. These settings determine the source code that the deployment process builds and deploys on the {KIE_SERVER}.
*** If you deployed the *Immutable Server - Monitor* option and want to connect the server to the monitoring infrastructure:
**** Under *Router integration*, the service name of the `rhpam-immutable-mon-smartrouter` service.
**** Under *Controller integration*, the service name of the `rhpam-immutable-mon-rhpamcentrmon` service and the admin username and password that you set in the *Immutable Server - KIE Process Server* option.
+
[IMPORTANT]
====
Avoid each of the following combinations of settings. These combinations produce an invalid environment.

* *Process server*>**Database type** `H2` and *Process server*>**Number of replicas** exceeding `1`.
* *Process server*>**Database type** `External` and *Process server*>**Sets of Process Servers** exceeding `1`.
* *Red Hat - Single Sign-On* configured and  *Process server*>**Sets of Process Servers** exceeding `1`.
====
+
. If you are using the *External* database type for the {KIE_SERVER} in the *Authoring*, *Immutable Server - Process Server*, or *Managed Environment* option, set the parameters under the *External Database* heading. Set the host, port, database name, and database JDBC URL to the correct values for your database server. Use the following values for the other fields:
+
** *Driver name*: The driver for the server, depending on the server type:
+
*** mysql
*** postgresql
*** mariadb
*** mssql
*** db2
*** oracle
*** sybase
+ 
** *Dialect class* (`KIE_SERVER_EXTERNALDB_DIALECT`): The Hibernate dialect for the server, depending on the server type:
+
*** `org.hibernate.dialect.MySQL5Dialect` (used for MySQL and MariaDB)
*** `org.hibernate.dialect.PostgreSQLDialect` 
*** `org.hibernate.dialect.SQLServer2012Dialect` (used for MS SQL)
*** `org.hibernate.dialect.DB2Dialect`
*** `org.hibernate.dialect.Oracle12cDialect`
*** `org.hibernate.dialect.SybaseASE15Dialect`
+
. If you created a custom image for using an external database server other than MySQL or PostgreSQL, as described in <<externaldb-build-proc>>, you must also set the *Process Server Image Stream Name* parameter (under the *Process Server* heading) to the following value:
+
** For Microsoft SQL Server, `{PRODUCT_INIT}{ENTERPRISE_VERSION_SHORT}-kieserver-mssql-openshift`
** For MariaDB, `{PRODUCT_INIT}{ENTERPRISE_VERSION_SHORT}-kieserver-mariadb-openshift`
** For IBM DB2, `{PRODUCT_INIT}{ENTERPRISE_VERSION_SHORT}-kieserver-db2-openshift`
** For Oracle Database, `{PRODUCT_INIT}{ENTERPRISE_VERSION_SHORT}-kieserver-oracle-openshift`
** For Sybase, `{PRODUCT_INIT}{ENTERPRISE_VERSION_SHORT}-kieserver-sybase-openshift`
+
. Click *Next* to commence deployment.
+
After deploying the environment, you can access it using the HTTPS routes displayed in the OpenShift Web console. HTTP requests are redirected to HTTPS.

IMPORTANT: After deploying the service, you can scale the {KIE_SERVER} pods up and down as necessary. Do not scale the database pods.
{'fraction_non_alphanumeric': 0.0895582329317269, 'fraction_numerical': 0.0036144578313253013, 'mean_word_length': 5.113747954173486, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 17, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2557912', 'n_tokens_mistral': 2050, 'n_tokens_neox': 1962, 'n_words': 950}