This chapter contains the requirements when capturing from a PostgreSQL database and replicating to supported target databases.
SharePlex supports replication for the PostgreSQL Database as a Service as source, according to the details below.
For information regarding supported source and target operating systems with specific database versions, see the Compatibility Matrix for Supported Operating Systems and Target Platforms section. To view compatibility across operating systems for remote replication, see Compatibility Across Operating Systems (Remote Collection and Posting).
Amazon Web Services:
Amazon RDS for PostgreSQL
Amazon Aurora
Microsoft Azure:
Azure Database for PostgreSQL Flexible Server
Google Cloud Platform:
Cloud SQL for PostgreSQL
Alloy DB
Note: PostgreSQL Database as a Service supports only logical replication.
PostgreSQL 13.x , 14.x, 15.x, 16
ODBC drivers for Community Edition: postgresql13-odbc-13.02.0000, postgresql14-odbc-13.02.0000,postgresql15-odbc-16.00.0000, and postgresql16-odbc-16.00.0000
CHAR
VARCHAR
SMALLINT
INT
BIGINT
NUMERIC
REAL
DOUBLE PRECISION
DATE
TIMESTAMP [p]
TIMESTAMP
TIMESTAMP [p] [WITH TIME ZONE]
TEXT
SharePlex supports DML operations on tables. DML can be replicated from a PostgreSQL Database as a Service as source to a PostgreSQL target.
SharePlex supports the following DML operations on tables:
The target table must support the column types that are being replicated from the source PostgreSQL table.
Currently, SharePlex does not support DDL operations when replicating data from a PostgreSQL Database as a Service as source to a PostgreSQL target. It only supports tables as objects for data replication.
SharePlex supports replication from PostgreSQL Database as a Service to Kafka, according to the details below.
For information regarding supported source and target operating systems with specific database versions, see the Compatibility Matrix for Supported Operating Systems and Target Platforms section. To view compatibility across operating systems for remote replication, see Compatibility Across Operating Systems (Remote Collection and Posting).
Apache Kafka 3.6.1 and 3.8
Confluent Kafka 7.6
We test and reproduce issues against:
Apache Kafka
Confluent Kafka
NOTE: If you would like to use a different vendor who provides their own Kafka distribution or provides a Kafka compliant interface, you are welcome to do so. From a support perspective, our support and development teams will share any Kafka broker errors that SharePlex receives and also ensure SharePlex itself is working properly to capture data, the target configuration formats in SharePlex are correct, and the SharePlex poster is posting or attempting to post according to the Kafka versions under support. If there are SharePlex issues with Kafka support that can be reproduced on Apache Kafka or otherwise demonstrated to be definitely associated with SharePlex, our team will address those as standard Kafka issues.
XML format
For XML supported data type information, see XML format supported data types.
JSON format
For JSON supported data type information, see JSON format supported data types.
SharePlex supports DML operations on tables. DML can be replicated from a PostgreSQL Database as a Service as source to a Kafka target.
SharePlex supports the following DML operations on tables:
SharePlex does not support DDL operations and objects when replicating data from a PostgreSQL Database as a Service as source to a Kafka target.
SharePlex supports replication from PostgreSQL Database as a Service to Oracle, according to the details below.
For information regarding supported source and target operating systems with specific database versions, see the Compatibility Matrix for Supported Operating Systems and Target Platforms section. To view compatibility across operating systems for remote replication, see Compatibility Across Operating Systems (Remote Collection and Posting).
Oracle 19c, 21c, and Oracle ADB for autonomous transaction processing database 19c.
For detailed notes on the supported Oracle versions, see the Notes section under System Requirements and Conditions of Support When Replicating from Oracle for Oracle-to-Oracle replication.
Oracle Cloud Infrastructure
Enterprise Standard Edition
Enterprise Edition High Performance
Enterprise Edition Extreme Performance
Oracle Database@Azure
Oracle Database@AWS
For information on the conditions of support for Oracle Cloud Infrastructure, see the System Requirements and Conditions of Support When Replicating from Oracle subsection added under Supported Target Cloud Platforms in the Oracle-to-Oracle replication section.
Amazon Web Services
Microsoft Azure
Azure Virtual Machine (IaaS)
UTF 8
SharePlex supports the following data types for replication from PostgreSQL Database as a Service to Oracle:
| PostgreSQL | Oracle |
|---|---|
| INT | NUMBER / INT |
| REAL | BINARY_FLOAT / NUMBER |
| SMALLINT | NUMBER |
| BIGINT | NUMBER |
| NUMERIC | NUMBER |
| DOUBLE PRECISION | BINARY_DOUBLE / NUMBER |
| CHAR(1:2000) | CHAR(n) |
| CHAR(2001:) | CLOB |
| CHAR(1:1000) | NCHAR(n) |
| VARCHAR(1:4000) | VARCHAR2(n) |
| VARCHAR(4001:) | CLOB |
| VARCHAR | CLOB |
| VARCHAR(1:2000) | NVARCHAR2(n) |
| TEXT | CLOB / NCLOB |
| DATE | DATE |
| TIMESTAMP(0) | DATE |
| TIMESTAMP(0) | TIMESTAMP(0) |
| TIMESTAMP | TIMESTAMP / TIMESTAMP [(fractional_seconds_precision)] WITH LOCAL TIME ZONE |
| TIMESTAMP WITH TIME ZONE | TIMESTAMP WITH TIME ZONE |
| BOOLEAN | CHAR (1)* |
| BYTEA | BLOB |
*NOTE: For PostgreSQL Physical or Logical replication, BOOLEAN values will be replicated as 1/0 in a CHAR(1) column on the Oracle target.
SharePlex supports the following PostgreSQL data types for replication from PostgreSQL Database as a Service to Oracle when conflict resolution is configured:
VARCHAR
SMALLINT
INT
BIGINT
NUMERIC
DATE
CHAR
TIMESTAMP(0)
TIMESTAMP
TIMESTAMP WITH THE TIME ZONE
TIME
TIME WITH TIME ZONE
BOOLEAN
SharePlex supports DML operations on tables. DML can be replicated from a PostgreSQL Database as a Service to an Oracle target.
SharePlex supports the following DML operations on tables:
Singular and bulk operation - Insert
Singular and bulk operation - Update with key(s)/ non key(s)
Singular and bulk operation - Delete with key(s)
Above operations with rollback/savepoint
The target table must support the column types that are being replicated from the source PostgreSQL table.
Currently, SharePlex does not support DDL operations when replicating data from a PostgreSQL Database as a Service as source to an Oracle target. It only supports tables as objects for data replication.
SharePlex supports replication from PostgreSQL Database as a Service to PostgreSQL, according to the details below.
For information regarding supported source and target operating systems with specific database versions, see the Compatibility Matrix for Supported Operating Systems and Target Platforms section. To view compatibility across operating systems for remote replication, see Compatibility Across Operating Systems (Remote Collection and Posting).
PostgreSQL 13.x , 14.x, 15.x, 16, and 17
Enterprise Database (EDB) 15.x and 16
Fujitsu Enterprise PostgreSQL 15 SP2, 16, and 17
AlloyDB Omni 15.5.x
ODBC drivers for Community Edition: postgresql13-odbc-13.02.0000, postgresql14-odbc-13.02.0000,postgresql15-odbc-16.00.0000, and postgresql16-odbc-16.00.0000
ODBC drivers for Enterprise Edition (EDB): edb-odbc-13.02.0000 and edb-odbc-16.00.0000.01
Amazon Web Services:
Amazon EC2 (IaaS) Virtual Machine
Amazon RDS for PostgreSQL
Amazon Aurora
Microsoft Azure:
Azure Virtual Machine (IaaS)
Azure Flexible Server
Google Cloud Platform:
Cloud SQL for PostgreSQL
AlloyDB for PostgreSQL
UTF 8
SharePlex PostgreSQL supports the following data types for replication from PostgreSQL Database as a Service to PostgreSQL:
SharePlex supports DML operations on tables. DML can be replicated from a PostgreSQL Database as a Service to a PostgreSQL target.
SharePlex supports the following DML operations on tables:
The target table must support the column types that are being replicated from the source PostgreSQL table.
Currently, SharePlex does not support DDL operations when replicating data from a PostgreSQL Database as a Service as source to a PostgreSQL target. It only supports tables as objects for data replication.
SharePlex supports replication from PostgreSQL Database as a Service to Snowflake, according to the details below.
For information regarding supported source and target operating systems with specific database versions, see the Compatibility Matrix for Supported Operating Systems and Target Platforms section. To view compatibility across operating systems for remote replication, see Compatibility Across Operating Systems (Remote Collection and Posting).
Snowflake 8.38.2
ODBC driver requirement: from Snowflake 3.1.4 to 3.8
Microsoft Azure
Amazon Web Services
SharePlex supports the following data types for replication from PostgreSQL Database as a Service to Snowflake:
| PostgreSQL | Snowflake |
|---|---|
| TEXT | TEXT |
| INT | INT,INTEGER,NUMBER |
| CHAR(1:2000) | VARCHAR(n) |
| CHAR(2001:) | VARCHAR(n) |
| CHAR(n) | CHAR(n) |
| VARCHAR(1:4000) | VARCHAR(n) |
| VARCHAR(4001:) | VARCHAR(n) |
| VARCHAR | VARCHAR(n) |
| REAL | REAL |
| SMALLINT | SMALLINT |
| BIGINT | BIGINT |
| NUMERIC (whole number without fraction) | NUMERIC, DECIMAL |
| NUMERIC (fractional number) | FLOAT |
| DATE | DATE |
| DOUBLE PRECISION | DOUBLE PRECISION |
| TIMESTAMP | TIMESTAMP |
| TIMESTAMP_TZ | TIMESTAMP_TZ |
| BOOLEAN | BOOLEAN |
| TIME | TIME |
Char(n) data type - In PostgreSQL, Char(n) is a fixed-size data type. If you insert char data with a length less than "n" into the "Char(n)" column, the remaining slots (n - length) are padded with space to occupy the complete "n" memory positions. Snowflake uses VARCHAR(n) for char storage since Snowflake lacks a comparable fixed-length character data type and only saves char data up to its length. Live replication will ensure that char column data is correctly copied. However, if users are manually inserting data into Snowflake for the equivalent of a Char(n) PostgreSQL column, then the user will need to handle padding as well to occupy the full "n" length so that data will be in sync in both the source and target database.
Text data types - Snowflake Text data types have size limitation of 8 MB, so PostgreSQL’s TEXT data type replication will be restricted to max 8 MB size limit of equivalent counterpart. Refer table below.
| PostgreSQL Data type | Max Size | Snowflake Data type | Max Size |
|---|---|---|---|
| TEXT | unlimited | TEXT | 8 MB of unicode chars |
See Conditions of support for the additional conditions of support for the above-mentioned supported data types.
SharePlex supports DML operations on tables, with some conditions. DML can be replicated from an PostgreSQL Database as a Service to a Snowflake target.
SharePlex supports the following DML operations on tables when replicating data from an PostgreSQL Database as a Service to the Snowflake target:
Singular and bulk operation - Insert with key(s)/ non key(s)
Singular and bulk operation - Update with key(s)/ non key(s)
Singular and bulk operation - Delete with key(s)/ non key(s)
| Limitations:
The following DML operations related limitations are observed while replicating data from PostgreSQL Database as a Service to Snowflake:
|
For additional information, see Supported Operations and Objects for DML Replication.
Currently, SharePlex does not support DDL operations when replicating data from a PostgreSQL Database as a Service as source to a Snowflake target. It only supports tables as objects for data replication.
SharePlex supports replication from PostgreSQL Database as a Service to SQL Server, according to the details below.
For information regarding supported source and target operating systems with specific database versions, see the Compatibility Matrix for Supported Operating Systems and Target Platforms section. To view compatibility across operating systems for remote replication, see Compatibility Across Operating Systems (Remote Collection and Posting).
SQL Server 2016, 2017, 2019 and 2022
ODBC driver requirement: ODBC 17.10.1.1-1 and 18.3.2.1-1
Amazon Web Services
Amazon EC2 (IaaS) Virtual Machine
Microsoft Azure
Azure Virtual Machine (IaaS)
Azure SQL Database
Azure SQL Managed Instance
SharePlex supports the following data types for replication from PostgreSQL Database as a Service to SQL Server:
| PostgreSQL | SQL Server |
|---|---|
| INT | INT |
| REAL | REAL |
| SMALLINT | SMALLINT |
| BIGINT | BIGINT |
| NUMERIC / DECIMAL | NUMERIC / DECIMAL |
| DOUBLE PRECISION | FLOAT |
| CHAR (1:8000) | CHAR(n) |
| CHAR (8001:) | VARCHAR (MAX) |
| CHAR (1:2000) | NCHAR (n) |
| VARCHAR (1:8000) | VARCHAR (n) |
| VARCHAR (8001:) | VARCHAR (MAX) |
| VARCHAR(1:2000) | NVARCHAR (n) |
| VARCHAR | VARCHAR (MAX) / TEXT |
| TEXT | TEXT / NTEXT / VARCHAR(MAX) |
| DATE | DATE |
| TIMESTAMP (p) | DATETIME2 (p) |
| TIMESTAMP | DATETIME2 |
| TIMESTAMP WITH TIME ZONE | DATETIMEOFFSET |
SharePlex supports DML operations on tables. DML can be replicated from a PostgreSQL Database as a Service to an SQL Server target.
SharePlex supports the following DML operations on tables:
The target table must support the column types that are being replicated from the source PostgreSQL table.
Currently, SharePlex does not support DDL operations when replicating data from a PostgreSQL Database as a Service as source to an SQL Server target. It only supports tables as objects for data replication.
The following is a list of known issues, including those attributed to third-party products, known to exist at the time of release.
| Issue ID | Known Issues | Component/ Feature |
|---|---|---|
| SPSQL-12113 | When users upgrade from SharePlex 12.0 to 12.2 on the Windows platform, the Sp_Utils desktop icon does not update to the new version. | Windows upgrade |
| SPSQL-12046 | The Repair option displays the window title as Uninstall & Button instead of Repair & Button. | Repair |
| SPSQL-12015 |
The un-installation option is not displayed in All Programs even after installing SharePlex. This issue occurs intermittently. It also occurs during an upgrade, the Uninstall icon points to the previous uninstaller in upgrade scenarios. Workaround: Use Windows Add or Remove Programs to uninstall SharePlex, or run uninstall.exe from the installation directory. |
Windows Installer |
| SPSQL-11993 |
During SharePlex un-installation, the sp_remote and sp_cop services are not automatically terminated if they are active. As a result, the un-installation does not complete successfully. Workaround: Manually stop the sp_remote or sp_cop services and rerun the SharePlex uninstallation.
|
Un-installation |
| SPSQL-11982 |
After aborting a failed SharePlex installation during node addition, the Windows installer does not automatically close the failure screen or roll back changes. Instead, it remains on the failed screen and incorrectly adds the failed node to sp_utils. Workaround: Reinstall SharePlex after manually stopping the SharePlex processes or services. The running processes and services will be notified during the SharePlex installation. |
Windows Installer |
| SPSQL-11732 |
The compare command displays the error_code=904 state=42S22 msg=[Oracle][ODBC][Ora] ORA-00904: "AMOUNT": invalid identifier when users attempt to compare horizontally partitioned tables in replication. This issue occurs when replicating data from PostgreSQL to Oracle. For example: In a Postgres-to-Oracle (P2O) setup, even though the column "amount" exists in both the source and target tables, the compare operation fails because Oracle treats unquoted identifiers as uppercase. In the partition definition - add partition to sales_scheme set name = highAmount and condition = "amount >= 10000" and route = 10.250.40.70@o.p19c the column amount is interpreted as AMOUNT on the Oracle side, which causes a mismatch during comparison. |
Compare |
| SPSQL-11137 |
Unable to uninstall SharePlex using Add or remove programs on Windows Server 2025. Workaround: Uninstall SharePlex by running unwise.exe located in the SharePlex installation directory. |
Uninstallation |
| SPSQL-11132 |
When users try to launch the SpUtils or SpClient utility on Windows Server 2025, the background console for SpUtils and SpClient also opens along with the main utility application. Workaround: Go to Settings > Terminal settings, and set the Terminal option to Windows Console Host. |
SpUtils, SpClient |
| SPSQL-11050 |
The monitoring script may fail to monitor processes and logs, and it does not generate alerts for stopped processes after running for an extended period of time. Workaround: Restarting the monitoring process restores normal alert generation. |
sp_client |
| SPSQL-10702 | When comparing tables in replication, setting the SP_SYS_JOB_HISTORY_RETENTION parameter to 1 and executing clear history jobid does not remove all logs as expected based on the parameter value. | Compare |
| SPSQL-10281 | SharePlex displays incorrect update count in Show Post Details when update operations are performed on table without any key, or update of key on table having key/s. These updates result in Delete+Insert transaction in Parquet File. | Parquet |
| SPSQL-8400 |
In the Compare/Repair process, the row count in the Oracle table might be outdated because it is initially fetched from the system table sys.tab$, which is not updated in real-time and depends on the DB stats analyzer process. As a result, users may encounter the error source vs target table size difference too large incorrectly in some cases. Workaround: Either wait for the row count to be updated in the system table by the stats analyzer process, or use the override option as suggested. |
Compare/Repair |
| SPSQL-5252 |
In the bi-directional replication of data from PostgreSQL 14.7 Google Cloud Platform to Oracle, the Poster process stops with an error when a user-defined procedure tries to resolve the conflicts that occurred on columns with a VARCHAR data type. This issue is observed if the update statement is triggered simultaneously in the same row on both source and target. |
Bi-directional replication |
| SPSQL-4858 | SharePlex displays the ORA-22990: LOB locators cannot span transactions error, and Compare results show out-of-sync data when users perform DML operations on data in replication after moving a LOB segment. This issue is observed on Oracle 23ai platform. | Compare |
| SPSQL-4764 | The Poster process fails to replicate data from Oracle 19c to the file target after a Truncate operation is performed on the replicated data. This issue specifically affects tables containing BFILE and SDO_GEOMETRY columns. | Poster |
| SPSQL-4982 | When there are multiple Named Queues set up in replication, after activating the config, the SharePlex Poster process displays the execute select pg_replication_origin_create ('sp_post_2600_7'); failed error upon its initial startup. However, after displaying the error, SharePlex automatically restarts the Poster process to resolve the issue. | Poster |
| SPSQL-8404 |
The Poster process stops with an error when users try to replicate a horizontally partitioned table with a case-sensitive schema, table name, and a single partitioning scheme from the Oracle to the PostgreSQL database. Workaround: Create separate partitioning schemes for each target table name and create a separate entry for each table in the config file. |
Poster |
| SPSQL-6104 | The SharePlex Poster process stopped due to an ORA-40441 error: JSON syntax error, triggered when users insert bulk JSON data for CLOB/NCLOB storage, which is stored as BASICFILE. | Poster |
| SPSQL-5630 | The Poster process stops due to an error when only the target table has a check constraint, and the inserted data violates that check constraint. | Poster |
| SPSQL-5454 | The SharePlex Poster process stops after activating the configuration for a hash partition on a target VM that has a '-' in its hostname. This issue is observed on the Windows platform. | Poster |
| SPSQL-5459 |
When inserting the same rows multiple times into a table without a primary key and then updating all rows, an OOS (out-of-sync) error message appears in the Poster log. This issue occurs for both tables with normal names and table names longer than 30 characters during Oracle to PostgreSQL replication. |
Poster |
| SPSQL-6117 | The undo_provision utility is not fully reverting all the changes made by the Provision utility. | Provision |
| SPSQL-5894 | When the Capture, Export, and Post queues have messages, and users run the Purge Config command, all queues are emptied as expected. However, error messages are observed in the source event logs. | Purge Config |
| SPO-24945 |
During Oracle to Kafka replication, the schema records of all tables are being replicated, not just the tables being replicated from Oracle to Kafka. Workaround: Set the schema value to 'no' to avoid sending the schema record. However, validate whether the schema record is used internally before applying this setting. |
Kafka |
| SPO-24922 | SharePlex does not support the RAISE INFO message on PostgreSQL databases. Poster stops with the Post stops error=-1 when trigger issues a RAISE [LABEL] error message. | RAISE INFO message |
| SPO-21339 | The SharePlex Capture process is getting stuck when users change the Oracle compatibility parameter from 11g to 12c. This issue is observed on the 12c 4 node RAC database. | Capture |
| SPO-20451 | Compare/Repair using [schema].[table] may not work on AIX 7.2 with Oracle 19c due to establishing a network connection. | Compare |
| SPO-20843 | Copy job status shows 'Locked' even when completed. | Copy/ Append |
| SPO-21993 |
While activating a config file with an Oracle SCN number, users are not able to delete a column in a DDL activity. |
DDL Drop Column |
| SPO-20205 | Oracle to Kafka supported data format: Kafka replicates the varray column data only in the XML format. Currently, Kafka does not replicate the varray column data in the JSON format. |
Kafka |
| SPO-20842 | On Oracle 19c processing large n-items can lead to OOS and/or missing commits. | LOBs, VARRAYs, XML |
| SPSQL-4971 | The tables are getting out-of-sync after users perform bulk DML operations on the CLOB column data. This issue has been observed while working on Oracle 21c. | Oracle 21c |
| SPO-22517 | Performance issue is observed during replication while using partition table over the cloud for MySQL and PostgreSQL. | Partition table |
| SPSQL-6609 | SharePlex displays an error when users attempt to create a database name in lowercase during pg_setup that matches an existing database name in uppercase on the system. | pg_setup |
| SPSQL-4982 | The SharePlex Poster process displays the Poster: execute select pg_replication_origin_create ('sp_post_xxxx_x'); failed error when creating an origin with logical replication for PostgreSQL to PostgreSQL replication. | Poster |
| SPSQL-5252 | The SharePlex Poster stops due to an error when attempting to resolve conflicts on VARCHAR columns in a PostgreSQL-Oracle bi-directional setup using a user-defined conflict resolution procedure. | Poster |
| SPO-19048 | Replication of tables with varray columns from an Oracle source to a non-Oracle target can get out of sync because Oracle doesn't include key information on updates. | varray columns |
| Issue ID | Known Issue | Component/ Feature |
|---|---|---|
| 29865658 | On Windows Server, Oracle 19c versions below 19.6 have an Oracle bug (29865658) that causes the SharePlex ora_setup, Reader, and Poster processes to get stuck. This bug is fixed in version 19.6 and later.To avoid this issue with SharePlex, either upgrade the Oracle 19c database to version 19.6 or higher. Users need to contact Oracle to obtain a patch for bug 29865658 or set the CLIENT_STATISTICS_LEVEL database parameter to 'OFF'. | Oracle |
| SR 3-33906406631 | After moving the LOB segment, users may encounter an 'ORA-22275' or 'ORA-22990' Oracle error when performing DML operations. Additionally, the Compare result may be displayed as out of sync. This issue is observed intermittently on Oracle 21c. See Oracle bug report SR 3-33906406631. | Oracle |
| 101806 | When replicating data from Oracle to MySQL, SharePlex Poster displays an error after performing the Update operation on columns with the data type integer and column values that are multiples of 1000. This issue is related to a defect in the MySQL database: https://bugs.mysql.com/bug.php?id=101806 | MySQL |
To use the license utilities, such as to view, add, or remove license keys, see the SharePlex License Utilities section in the SharePlex Reference guide or SharePlex Installation and Setup Guide. For more information, contact your account manager.
SharePlex 11 requires new license keys.
License keys issued for versions prior to 11.0 will be incompatible with SharePlex 11.x. Existing customers should obtain a new license key before installing and/or upgrading to SharePlex 11.x. To obtain a new license key, please refer to the Licensing Assistance page on the Support Portal.
SharePlex 11.x are available for installation on Linux and Unix platforms.
Customers who wish to replicate to and from sources and targets that run on Windows can either use the 10.x or 12.0 versions of SharePlex or use remote replication, where the SharePlex software runs on a Linux server. Please see the System Requirements sections for details on supported source/target combinations with remote replication.
Note: To upgrade from SharePlex 10.x to 11.0 or 11.1, a new SharePlex license key must be requested. However, to upgrade from SharePlex 11.0 to 11.1, the existing effective SharePlex license key can be utilized.
Understanding SharePlex licensing and platform requirements
SharePlex licenses have validity and usage limits according to specific platforms. For example, you must have a PostgreSQL license to use a PostgreSQL database and a Kafka license to use the Kafka platform.
Additionally, SharePlex supports multiple keys for situations where customers need two platforms on one server. For example, if a user is replicating data from an Oracle source to a Kafka target, where one SharePlex instance is serving as both the source and target, the SharePlex server would require both Oracle and Kafka licenses.
Installing a trial version
To install a trial version of SharePlex, users need to select the All Platforms option when prompted during installation of SharePlex or while running the splex_add_key utility. For additional information, see the Install SharePlex section in the SharePlex Installation Guide.
SharePlex installations can be run on FIPS-enabled servers on the Linux platform. No FIPS-specific configurations are required to run SharePlex installations on FIPS-enabled servers.
To align with CMVP (Cryptographic Module Validation Program) guidelines and strengthen data security, SharePlex supports cryptographic operations using the OpenSSL FIPS provider on Linux platform. It ensures that AES encryption algorithms used within SharePlex are executed through a validated cryptographic module, meeting FIPS 140-2 standards.
SharePlex OpenSSL FIPs settings:
| Component | Algorithm Used | Mode | Key Length | FIPS Compliance | Notes |
| Communication between SharePlex processes—such as COP to Command and Control, and data flow between Export and Import—can be secured. Refer to the sp_security section for instructions on enabling TLS security. |
To make the FIPS provider the default, use the following OpenSSL calls: OSSL_PROVIDER_load(NULL, "fips"); EVP_set_default_properties(NULL, "fips=yes"); |
FIPS | 256 | Yes | Used for TLS-encrypted secure communication between SharePlex source and target. |
| Provides additional AES-encrypted tunneling between Export and Import processes. Refer to SP_XPT_ENABLE_AES and SP_IMP_ENABLE_AES for configuration details. | AES | FIPS | 128/192/256 | Yes | Users can configure a key of the desired length to encrypt data. |
| Store sensitive information | AES | FIPS | 256 | Yes |
