(Glue-2502) Redshift Prerequisites
High-level summary of necessary steps (more details in https://datavard.atlassian.net/wiki/spaces/DATAVARD/pages/2229601380):
SAP Basis/Infrastructure tasks:
Basis team:
Java Connector: https://datavard.atlassian.net/wiki/spaces/DATAVARD/pages/2229602754
Creation of SNP_JAVA_CONN RFC:
Connection type: TCP/IP Connection.
Activation type: Registered Server Program.
Fill in the Program ID (e.g.): SNP_JAVA_CONNECTOR.
Creation of Technical SAP user for ABAP >JCO RFC Communication:
In the transport, you are provided with a template role with name /DVD/JCORFC (if you will use this role, do not forget to generate the profile in transaction PFCG).
Create System user, with role /DVD/JCORFC.
Granting access for external program SNP_JAVA_CONN to SAP gateway:
Check SMGW > GoTo > Expert Functions > External Security > Maintenance of ACL files whether external programs are allowed (=* or ProgramID).
SAP system (Operating system level):
Uploading Redshift JDBC driver to
/sapmnt/<SID>/global/security/dvd_conn/redshift
, more details can be found in (SM-2402) S3/Redshift Storage Setup | Redshift prerequisites.
Networking team:
Enabling outbound communication from the SAP system to AWS:
Port | Address |
---|---|
443 | s3.<region>.amazonaws.com |
5439 | <NameOfEndpoint>.<redshift>.redshift.amazonaws.com |
AWS team:
Creation of technical user in S3 (assigning appropriate policy is necessary) - more details can be found in https://datavard.atlassian.net/wiki/spaces/DATAVARD/pages/4510351548/SM-2402+S3+Redshift+Storage+Setup#S3-Prerequisites under section S3 Policy.
Redshift (SM-2402) S3/Redshift Storage Setup | Redshift prerequisites:
Redshift requires working S3 storage.
Creation of Redshift schema and database user.