Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

High-level summary of necessary steps (more details in (SM-2302) S3/Redshift Storage Setup ):

SAP Basis/Infrastructure tasks:

Basis team:

  1. Java Connector: (SM-Latest) Java Connector Setup

    1. Creation of SNP_JAVA_CONN RFC:

      1. Connection type: TCP/IP Connection.

      2. Activation type: Registered Server Program.

      3. Fill in the Program ID (e.g.): SNP_JAVA_CONNECTOR.

    2. Creation of Technical SAP user for ABAP >JCO RFC Communication:

      1. In 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).

      2. Create System user, with role /DVD/JCORFC.

    3. Granting access for external program SNP_JAVA_CONN to SAP gateway:

      1. Check SMGW > GoTo > Expert Functions > External Security > Maintenance of ACL files whether external programs are allowed (=* or ProgramID).

Networking team:

  1. Enabling outbound communication from the SAP system to AWS:

Port

Address

443

s3.<region>.amazonaws.com

AWS team:

  1. S3 storage https://datavard.atlassian.net/wiki/spaces/DATAVARD/pages/4206133264/SM-2302+S3+Redshift+Storage+Setup#id-(SM-2302)S3%2FRedshiftStorageSetup-S3prerequisites

    1. 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/4206133264/SM-2302+S3+Redshift+Storage+Setup#id-(SM-2302)S3%2FRedshiftStorageSetup-S3prerequisites under section S3 Policy.

  • No labels