Merge pull request #390 from emmurphy1/BXMSDOC-8404-main (apache#4454)

BXMSDOC-8404 main Note on bytea schema for postgresql incorrect

doc-content/enterprise-only/installation/eap-data-source-add-proc.adoc

@@ -4,7 +4,7 @@
 
 A data source is an object that enables a Java Database Connectivity (JDBC) client, such as an application server, to establish a connection with a database. Applications look up the data source on the Java Naming and Directory Interface (JNDI) tree or in the local application context and request a database connection to retrieve data. You must configure data sources for {KIE_SERVER} to ensure correct data exchange between the servers and the designated database.
 
-Typically, solutions using {PRODUCT} manage several resources within a single transaction. JMS for asynchronous jobs, events, and timers, for example. {PRODUCT} requires an XA driver in the datasource when possible to ensure data atomicity and consistent results. If transactional code for different schemas exists inside listeners or derives from hooks provided by the jBPM engine, an XA driver is also required. 
+Typically, solutions using {PRODUCT} manage several resources within a single transaction. JMS for asynchronous jobs, events, and timers, for example. {PRODUCT} requires an XA driver in the datasource when possible to ensure data atomicity and consistent results. If transactional code for different schemas exists inside listeners or derives from hooks provided by the jBPM engine, an XA driver is also required.
 
 Do not use non-XA datasources unless you are positive you do not have multiple resources participating in single transactions.
 
@@ -38,7 +38,7 @@ If you are using PostgreSQL or Oracle in conjunction with Spring Boot, you must
 +
 [NOTE]
 ====
-The PostgreSQL DDL scripts create the PostgreSQL schema with auto-incrementing integer value (OID) columns for entity attributes annotated with `@LOB`. To use other binary column types such as BYTEA instead of OID, you must create the PostgreSQL schema with the `postgresql-bytea-jbpm-schema.sql` script and set the {PRODUCT} `org.kie.persistence.postgresql.useBytea=true` flag. Do not use the `postgresql-jbpm-lo-trigger-clob.sql` script when creating a BYTEA-based schema. {PRODUCT} does not provide a migration tool to change from an OID-based to a BYTEA-based schema.
+The PostgreSQL DDL scripts create the PostgreSQL schema with auto-incrementing integer value (OID) columns for entity attributes annotated with `@LOB`. To use other binary column types such as BYTEA instead of OID, you must create the PostgreSQL schema with the `postgresql-bytea-jbpm-schema.sql` script and set the {PRODUCT} `org.kie.persistence.postgresql.useText=true` and `org.kie.persistence.postgresql.useBytea=true` flags. Do not use the `postgresql-jbpm-lo-trigger-clob.sql` script when creating a BYTEA-based schema. {PRODUCT} does not provide a migration tool to change from an OID-based to a BYTEA-based schema.
 ====
 
 . Open `_EAP_HOME_/standalone/configuration/standalone-full.xml` in a text editor and locate the `<system-properties>` tag.