ssh -i /path/to/my_instance_keyfile.pem ec2-user@hxehost
ec2-user
OS user, I need to check and satisfy the installation prerequisites, specifically OS compatibility and Java 1.8 installation.root
, that's why first step sudo su -
.sudo su -
cat /etc/os-release
zypper search openjdk
zypper install -y java-1_8_0-openjdk
java -version
You can use SAP JVM too.
cd /tmp/
wget --no-cookies \
--header "Cookie: eula_3_1_agreed=tools.hana.ondemand.com/developer-license-3_1.txt" \
"https://tools.hana.ondemand.com/additional/sapcc-2.13.0-linux-x64.zip" \
-P /tmp/
unzip /tmp/sapcc-*-linux-*.zip
rpm -i com.sap.scc-ui-*.rpm
systemctl status scc_daemon
Please note that the version available at the time of writing this article was 2.13, but can be different at the time of reading. Check the current version at https://tools.hana.ondemand.com/#cloud.
curl --insecure https://hxehost:8443/
, but it is not available from the Internet, as I need to enable a rule allowing access to its port 8443
.aws
CLI instead of the AWS Cockpit.8443
(my EC2 instance has a name HXE02
; replace it and other technical names with ones from your environment):#Set the AWS region
export AWS_REGION=eu-central-1
#Get Instance's VPC ID
aws ec2 describe-instances --filters "Name=tag:Name,Values=HXE02" \
--query "Reservations[].Instances[0].NetworkInterfaces[0].VpcId[]"
#Create a new security group
aws ec2 create-security-group --vpc-id vpc-02708f64c1f7ef868 \
--group-name CloudConnector \
--description "Allow 8443 access to Cloud Connector"
#Add and ingress rule
aws ec2 authorize-security-group-ingress --group-id sg-07a8fbf91114b35e9 \
--protocol tcp --port 8443 --cidr 0.0.0.0/0
#Display security group's ingress rules
aws ec2 describe-security-groups --group-id sg-07a8fbf91114b35e9 \
--query "SecurityGroups[].IpPermissions"
#Get instance Network Interface ID
aws ec2 describe-instances --filters "Name=tag:Name,Values=HXE02" \
--query "Reservations[].Instances[0].NetworkInterfaces[0].NetworkInterfaceId"
#Get assigned security groups
aws ec2 describe-network-interfaces --filters "Name=network-interface-id,Values=eni-0071160c754b88c6c" \
--query "NetworkInterfaces[].Groups[].GroupId"
#Get Instance ID
aws ec2 describe-instances --filters "Name=tag:Name,Values=HXE02" \
--query "Reservations[].Instances[0].InstanceId"
#Set security groups
aws ec2 modify-instance-attribute --instance-id i-033f738d907b0773f \
--groups sg-0e43ac22a862322ef sg-07a8fbf91114b35e9
https://3.65.225.179:8443/
.From my local laptop, I can open it as well on https://hxehost:8443/
, because it is the same host running SAP HANA, express edition.
SystemDB
database (port 39013
) in this case.-- DROP REMOTE SOURCE "AWS_VITAL_HXE02_SYSTEMDB_SYSTEM" CASCADE;
CREATE REMOTE SOURCE "AWS_VITAL_HXE02_SYSTEMDB_SYSTEM"
ADAPTER "hanaodbc"
CONFIGURATION '
Driver=libodbcHDB.so;
ServerNode=aws-vitaliy-hxe02:39013;
dmlMode=readonly;
use_haas_socks_proxy=true;
'
WITH CREDENTIAL TYPE 'PASSWORD' USING 'user=SYSTEM;password=myPa$$w0rd';
CALL CHECK_REMOTE_SOURCE('AWS_VITAL_HXE02_SYSTEMDB_SYSTEM');
CONFIGURATION
contains a mix of the remote source's properties, like dmlMode
and extra properties, like use_haas_socks_proxy
,useHaasSocksProxy
and use_haas_socks_proxy
can be used,USERS
in SAP HANA on-prem then.CREATE VIRTUAL TABLE "DBADMIN"."V_HXE_USERS"
AT "AWS_VITAL_HXE02_SYSTEMDB_SYSTEM"."<NULL>"."SYS"."USERS";
SELECT * FROM "DBADMIN"."V_HXE_USERS";
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
30 | |
23 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
5 | |
4 |