Guru Of Geeks

View List of Available SDK Names Use this command to view a list of available SDK names for the product installation: managesdk.sh -listAvailable The following shows sample returned information. Set the command default to the version 7.0 SDK Use this command to set the command default to the version 7.0 SDK: managesdk.sh -setCommandDefault -sdkname 1.7_64 The following shows sample returned information. Set the New Profile Default to the Version 7.0 SDK Use this command to set the new profile default to version 7.0 SDK: managesdk.sh -setNewProfileDefault -sdkname 1.7_64 The following shows sample returned information. If Profiles Already Exist, Enable the Profiles to use the Version 7.0 SDK If profiles already exist, use this command to enable the profiles to use the version 7.0 SDK: managesdk.sh -enableProfileAll -sdkname 1.7_64 -enableServers The following shows sample returned information.

Open the global.ini file  /hana/shared/$SID/global/hdb/custom/config/ global.ini   ​ ​ Restart the services.

Secure the communication between HANA Server and HANA Studio through SSL. It is highly recommended when there are lot of sensitive data handled in the system, which you want to secure from the middle-man attacks. There could be multiple documents available in SCN on this topic, but here I wants to show my experience on setting this up, in short time. Pre-requisites: HANA Server is installed and running HANA studio is installed in the local system Access to the HANA server Putty / WinSCP tools HANA Server and client without SSL configured: Steps need to be performed in HANA Server: Login to HANA server system using Putty, as a root user and check if the libssl.so file exists. If not, create a symbolic link to libssl.so.0.9.8. Now login to HANA server system, as a "<sid>adm" user. Create the Root Certificate: Go to Home directory "/usr/sap/<sid>/home" Create directory with a same ".ssl" Get into ".ssl" directory    4.  Execute the f...

https://github.com/satterly/AWSCloudFormation-samples

Setup pip install git+git:// github.com/artsy/jenkins-backup-s3.git Configure S3 and IAM Create an S3 bucket to store backups. Create an IAM role with STS:AssumeRole and a trust Service ec2.amazonaws.com . The IAM role must have the   GetObject ,   CreateObject ,   DeleteObject   and   ListBucket   S3 permissions for that bucket. Usage Setup with cron for ideal usage. backup-jenkins {OPTIONS} {COMMAND} {COMMAND_OPTIONS} Options can be set directly or via and environment variable. The only required option is your S3 bucket: backup-jenkins --bucket={BUCKET_NAME} Other available options are: Bucket prefix (defaults to "jenkins-backups"): backup-jenkins --bucket-prefix={BUCKET_PREFIX} Bucket region (defaults to "us-east-1"): backup-jenkins --bucket-region={BUCKET_REGION} Available commands: create restore list delete prune Run   backup-jenkins {COMMAND} --help   for command-specific options. Running a daily backup on Jenkins Create a new item in Jenkins and configur...

Two Databases ----------------------- Step 1: Go to db2 prompt db2=> Step 2 (Optional) Create database if necessary create database Tom create database Jerry Step 3: Connect to DB1 and create table (Example Tom) (Optional) connect to tom create table db2inst1.tab1 (cod1 int) insert into db2inst1.tab1 values (1) Step 4: Connect to DB2 and create table (Example Jerry) connect to jerry create table db2inst1.tab2 (name1 char) insert into db2inst1.tab2 values ('a') Step 5: Create server and mappings in 1st DB (Tom) to access 2nd DB (Jerry) connect to tom create server fedserver TYPE DB2/UDB VERSION 10.5 WRAPPER drda  AUTHORIZATION "db2inst1" password "******" OPTIONS(DBNAME 'jerry') create user mapping for db2inst1 SERVER fedserver OPTIONS(REMOTE_AUTHID 'db2inst1',REMOTE_PASSWORD '******') create nickname mytable for fedserver.db2inst1.tab1 Step 6: Executing Select statement from 1st Db (Tom) to query resu...

Mule Management Console which is also known as  MMC  in short,  is a centralizes management and monitoring functions for all our on-premise  Mule ESB Enterprise  deployments, that includes running as a standalone instances, as a cluster, or embedded in application servers. MMC   as an enterprise management and monitoring tool is designed specifically for Mule on-premises instances. It provides all the functionality for managing and monitoring running Mule on premises servers, Mule clusters, deployed applications within Mule servers, and the flows within those applications. Another important feature is it also provides ways of looking at specific transactions through pre-defined business events, as well as transactions in flight. MMC   by default supports internal   derby   database to persist environment and transaction data. If we start our   MMC   application under   Apache Tomcat   server, we can see under the   bin   folder there is a folder named as   mmc-data   is created whe...