Skip to Content

Hopefully some of you already tried our existing SAP NetWeaver BW on SAP HANA with SAP BusinessObjects BI trial and had a great experience.

Our trial is now available for a little over 4 months and so far we have :

  • Over 1400 people that activated the 30 day trial
  • Over 150.000 hours of usage

In case you would like to hear from another customer, what they did with the BW on HANA Trial, take a look at David’s experience here.

So why am I writing this today ?

Because I proudly announce the updated version of our SAP NetWeaver BW on SAP HANA with SAP BusinessObjects BI Trial.

Our trial now includes:

  • SAP NetWeaver BW 7.4 on SAP HANA SP07
  • SAP BusinessObjects BI 4.1
  • New eclipse based BW modelling
  • Updated exercises based on those new releases

In addition we also are making the 244 GB memory instances available for the BW on HANA part (Amazon AWS Instance : cr1.8xlarge).


So here is what you need:


  • Go and use it – simple as that.

Here some additional resources:

Please remember that the software is free of charge, but that you will be charged for the Amazon AWS hosting costs, which is around 4.50 USD per hour when the system is running.

To report this post you need to login first.

38 Comments

You must be Logged on to comment or reply to a post.

    1. Ingo Hilgefort Post author

      Hello Srikanth,

      it states clearly in any material for the BW on HANA Trial that you will have to pay the Amazon AWS costs (around 4.50 USD per hour) and it also shows in the “Getting started” how you can stop and start the systems.

      So it should come as a surprise that you do have to pay for the Amazon AWS costs.

      regards

      Ingo Hilgefort, SAP

      (0) 
        1. Ingo Hilgefort Post author

          Hello Srikanth,

          you see where it says below the button that it says :

          Separate Amazon Web Services fees apply.

          and it states the exact costs in the getting started material which is shown on the resources tab.

          regards

          Ingo Hilgefort, SAP

          (0) 
            1. Ingo Hilgefort Post author

              Hello Srikanth

              it has been there since the beginning of the page and it is pretty obvious and like I said it is also pretty clearly stated in the Getting started material for the trial

              regards

              Ingo Hilgefort, SAP

              (0) 
              1. srikanth mandalapu

                Agreed, I have tried HANA Trial on cloudshare and I was not charged for the 1st month so I assumed that this one is also free for the first month. 😯

                (0) 
              2. Harald Bronner

                Hello,

                I would like to know which EBS volumes are being used for the 2 instances, because the cost of the volumes don’t vary (regardless if the instances are stopped) and

                these costs can be from about 30$ to about 250$. So I think it’s important to know.

                Thanks in advance

                (0) 
                1. Ingo Hilgefort Post author

                  Hello Harald,

                  if you are interested in that level of detail I would suggest that you setup an instance of the BW trial into your Amazon AWS account, stop the system and take a look at the details in your own Amazon Account and you can then – if you want – terminate the instance right after that.

                  regards

                  Ingo Hilgefort

                  (0) 
                2. Ingo Hilgefort Post author

                  Hello Harald,

                  in addition during the process of setting up the instance you have the option to select “Standard” or “Provisioned IOPS” for the volumes.

                  regards

                  Ingo Hilgefort, SAP

                  (0) 
    1. Ingo Hilgefort Post author

      Hello Sven,

      sorry for that experience and Thank you for bringing it up.

      we will look into this right away and address it.

      regards

      Ingo Hilgefort, SAP

      (0) 
  1. sreenadh M.V

    Hi Ingo Hilgefort,

    Firstly thanks to SAP, the demo system is amazing, was able to explore more features of HANA on BW7.4.

    There are some issues with other tools such as Predicitve analytics, BO e.t.c license’s are expired. Can you please have a look. Also if its not you, please advise me on any other channel who can address this issue.

    regards

    Sree.

    (0) 
  2. Sam Mureithi

    Hello Everyone,

    I have been using the BW on HANA trial with no problems. But yesterday I started getting the error below every time I try to start the A4H Instance. Any help to resolve this will be highly appreciated.

    Sam

    A4H Instance.jpg

    (0) 
    1. Ingo Hilgefort Post author

      Hello Sam,

      did you create a new set of instances yesterday or was this an existing instance that you simply restarted ?

      Could you see if a restart via the SAP Cloud Appliance Library console and a login with user “administrator” (and the master password) solve the issue ?

      thanks

      Ingo Hilgefort, SAP

      (0) 
  3. King raja

    Hello Ingo

    thanks for the great opportunity . i just registered in AWS , its says i have free account for one year

    Thank you for creating an Amazon Web Services (AWS) account. For the next 12 months, you will have free access to compute, storage, database, and application services.


    so does it mean i dont have to pay the hourly charges ?


    regards

    Kumar

    (0) 
    1. Ingo Hilgefort Post author

      Hello Kumar,

      pretty sure that we did not create an AWS account for you and a AWS account itself might be free but any activity that you do, you will be charged for. You can find the details in the Getting Started material and you will also see a cost estimate when you create the instances.

      regards

      Ingo Hilgefort

      (0) 
  4. Sangeeta Gupta

    THIS HAS BEEN SOLVED


    Deletion and Recreation of instance resolved it

    …………………………………………………………..

    Ingo

    I cannot seem to see the green in status. Just says undermined. However as Administrator I can logon to the frontend IP but then cant start the SAP server. On right-click the system freezes. Once I got through and started but again got an error.

    I cant see anywhere I can raise this, hence posting it here.

    On Amazon AWS site, 1 instance is running with green status.

    Thanks in advance.

    Screenshots attached./wp-content/uploads/2014/10/undefined_556171.pngSapmmc.png

    (0) 
    1. Ingo Hilgefort Post author

      Hello Sangeeta,

      could you terminate the current instance and de-active the current solution ?

      then activate the solution again and create a new set of instance.

      It takes around 40 minutes until the system is up and running correctly

      regards

      Ingo

      (0) 
    2. King raja

      Hi sangeeta

      did you find a answer for this ?

      i am getting the same error ,already terminated and created the instance twice . still not working . i am also getting charged for this . how did you solve the issue

      regards

      Kumar

      (0) 
  5. Sangeeta Gupta

    Thanks Ingo

    I did that (twice actually) and successfully logged on into BW but once I suspend the instance and reactivate, the server will just not start. Why is this happening?

    (Either it starts automatically, if it ever does or it does not accept the credentials when I manually want to start a server as per document – Linux credentials as per the document)

    Sangeeta

    (0) 
    1. Manfred Stein

      Hi Sangeeta

      Can you clarify what you mean by …does not accept the credentials …

      If you cannot log on to the Linux server on OS level using the PEM key file, we have a small problem, as the proposed fix Suspend and Resume does not work all the time in CAL

      requires you to log on to the OS of the BW backend server.

      Otherwise just give the proposed solution a try. We are just about to fix this problem for freshly created instances btw

      Manfred

      (0) 
  6. Ingo Hilgefort Post author

    Hello Tobias,

    as part of the Trial landscape you can not upload custom objects. The trial landscape comes with a set of predefined scenarios.

    In case you are looking to create customer objects or custom code, I would suggest you either look at the Developer Edition for the BW system or you consider the subscription to the SAP Cloud Appliance Library.

    best regards

    Ingo Hilgefort

    (0) 
  7. King raja

    Hi everybody ,

    has anyone tried the entire flow ? just wanted to know how much did you billing  come upto ? or how much time ?

    just want to be prepared ! saw some comments about it being 1000 dollars ,

    Thanks

    regards

    Kumar

    (0) 
    1. Ingo Hilgefort Post author

      Hello Mahesh,

      the billing is done per hour when the system is running and each of the appliances also have a “Getting Started” guide which shows the per hourly cost.

      in addition you will be shown a forecast in the UI.

      Also keep in mind that the default behavior for trials is, that the system will be stopped after 8 hours, unless you configure it differently

      regards

      Ingo Hilgefort

      (0) 
  8. Sangeeta Gupta

    I am using BW on HANA SP8.0 trial and according to documentation I should be able to connect using local GUI but I cant. I can connect using RDP client GUI, which means server is running.

    Also I cant make any RFC connection from our ECC system, although BI setup has developer as remote connect and SALE etc connection seem alright.

    Please can you help.

    PS: Solved. Opening the port solved it

    (0) 
    1. Ingo Hilgefort Post author

      Hello Sangeeta,

      the BW on HANA Trial comes with a server and a frontend part. the fronted part does provide you with the SAP GUI part.

      In case you would like to logon with your local SAP GUI you would have to open up the ports.

      In regards to connecting your own ERP system, please keep in mind that this is a trial system – not a system for any type of prototyping or a proof of concept.

      regards

      Ingo Hilgefort

      (0) 
  9. Sangeeta Gupta

    Ingo,

    I dont know if this is something you can help with. We are trying to connect to MSSQL outside of trial environment and have opened the ports. We can reach the server from outside and outside world from inside. (so thats not a problem)

    We are trying to install ODBC 2.3.0 which is requirement for MSSQL 2012. However we get a C compiler path error. We have tried man gcc, man cc and several other commands and have tried to locate c compiler program. We cant seem to find it.

    I have logged into root folder as bihost. (see attachment).

    Am I missing something?

    Can and should I install C compiler and what should be the path (how to set)?

    Attached screenshots.

    SG

    C Compiler.PNG

    error log

    This file contains any messages produced by compilers while

    running configure, to aid debugging if configure makes a mistake.

    It was created by unixODBC configure 2.3.0, which was

    generated by GNU Autoconf 2.64.  Invocation command line was

      $ ./configure

    ## ——— ##

    ## Platform. ##

    ## ——— ##

    hostname = bihost

    uname -m = x86_64

    uname -r = 3.0.101-0.35-ec2

    uname -s = Linux

    uname -v = #1 SMP Wed Jul 9 11:43:04 UTC 2014 (c36987d)

    /usr/bin/uname -p = unknown

    /bin/uname -X     = unknown

    /bin/arch              = x86_64

    /usr/bin/arch -k       = unknown

    /usr/convex/getsysinfo = unknown

    /usr/bin/hostinfo      = unknown

    /bin/machine           = unknown

    /usr/bin/oslevel       = unknown

    /bin/universe          = unknown

    PATH: /sbin

    PATH: /usr/sbin

    PATH: /usr/local/sbin

    PATH: /root/bin

    PATH: /usr/local/bin

    PATH: /usr/bin

    PATH: /bin

    PATH: /usr/bin/X11

    PATH: /usr/X11R6/bin

    PATH: /usr/games

    PATH: /usr/lib/mit/bin

    PATH: /usr/lib/mit/sbin

    ## ———– ##

    ## Core tests. ##

    ## ———– ##

    configure:2732: checking for a BSD-compatible install

    configure:2800: result: /usr/bin/install -c

    configure:2811: checking whether build environment is sane

    configure:2861: result: yes

    configure:3002: checking for a thread-safe mkdir -p

    configure:3041: result: /bin/mkdir -p

    configure:3054: checking for gawk

    configure:3070: found /usr/bin/gawk

    configure:3081: result: gawk

    configure:3092: checking whether make sets $(MAKE)

    configure:3114: result: yes

    configure:3199: checking for gawk

    configure:3226: result: gawk

    configure:3241: checking for bison

    configure:3271: result: no

    configure:3241: checking for byacc

    configure:3271: result: no

    configure:3292: checking for style of include used by make

    configure:3320: result: GNU

    configure:3390: checking for gcc

    configure:3420: result: no

    configure:3483: checking for cc

    configure:3530: result: no

    configure:3586: checking for cl.exe

    configure:3616: result: no

    configure:3640: error: in `/my_odbc_drivers/unixODBC-2.3.0′:

    configure:3643: error: no acceptable C compiler found in $PATH

    See `config.log’ for more details.

    ## —————- ##

    ## Cache variables. ##

    ## —————- ##

    ac_cv_env_CC_set=

    ac_cv_env_CC_value=

    ac_cv_env_CFLAGS_set=

    ac_cv_env_CFLAGS_value=

    ac_cv_env_CPPFLAGS_set=

    ac_cv_env_CPPFLAGS_value=

    ac_cv_env_CPP_set=

    ac_cv_env_CPP_value=

    ac_cv_env_LDFLAGS_set=

    ac_cv_env_LDFLAGS_value=

    ac_cv_env_LIBS_set=

    ac_cv_env_LIBS_value=

    ac_cv_env_YACC_set=

    ac_cv_env_YACC_value=

    ac_cv_env_YFLAGS_set=

    ac_cv_env_YFLAGS_value=

    ac_cv_env_build_alias_set=

    ac_cv_env_build_alias_value=

    ac_cv_env_host_alias_set=

    ac_cv_env_host_alias_value=

    ac_cv_env_target_alias_set=

    ac_cv_env_target_alias_value=

    ac_cv_path_install=’/usr/bin/install -c’

    ac_cv_path_mkdir=/bin/mkdir

    ac_cv_prog_AWK=gawk

    ac_cv_prog_make_make_set=yes

    ## —————– ##

    ## Output variables. ##

    ## —————– ##

    ACLOCAL=’${SHELL} /my_odbc_drivers/unixODBC-2.3.0/libltdl/config/missing –run aclocal-1.11′

    ALLOCA=”

    AMDEPBACKSLASH=’\’

    AMDEP_FALSE=’#’

    AMDEP_TRUE=”

    AMTAR=’${SHELL} /my_odbc_drivers/unixODBC-2.3.0/libltdl/config/missing –run tar’

    AR=”

    ARGZ_H=”

    AS=”

    AUTOCONF=’${SHELL} /my_odbc_drivers/unixODBC-2.3.0/libltdl/config/missing –run autoconf’

    AUTOHEADER=’${SHELL} /my_odbc_drivers/unixODBC-2.3.0/libltdl/config/missing –run autoheader’

    AUTOMAKE=’${SHELL} /my_odbc_drivers/unixODBC-2.3.0/libltdl/config/missing –run automake-1.11′

    AWK=’gawk’

    BIN_PREFIX=”

    CC=”

    CCDEPMODE=”

    CFLAGS=”

    CONVENIENCE_LTDL_FALSE=”

    CONVENIENCE_LTDL_TRUE=”

    CPP=”

    CPPFLAGS=”

    CYGPATH_W=’echo’

    DEFLIB_PATH=”

    DEFS=”

    DEPDIR=’.deps’

    DLLTOOL=”

    DRIVERC_FALSE=”

    DRIVERC_TRUE=”

    DRIVERS_FALSE=”

    DRIVERS_TRUE=”

    DSYMUTIL=”

    DUMPBIN=”

    ECHO_C=”

    ECHO_N=’-n’

    ECHO_T=”

    EGREP=”

    EXEC_PREFIX=”

    EXEEXT=”

    FGREP=”

    GREP=”

    HAVE_FLEX_FALSE=”

    HAVE_FLEX_TRUE=”

    ICONV_CHAR_ENCODING=”

    ICONV_UNICODE_ENCODING=”

    INCLTDL=”

    INCLUDE_PREFIX=”

    INSTALL_DATA=’${INSTALL} -m 644′

    INSTALL_LTDL_FALSE=”

    INSTALL_LTDL_TRUE=”

    INSTALL_PROGRAM=’${INSTALL}’

    INSTALL_SCRIPT=’${INSTALL}’

    INSTALL_STRIP_PROGRAM=’$(install_sh) -c -s’

    LD=”

    LDFLAGS=”

    LEX=”

    LEXLIB=”

    LEX_OUTPUT_ROOT=”

    LFLAGS=”

    LIBADD_CRYPT=”

    LIBADD_DL=”

    LIBADD_DLD_LINK=”

    LIBADD_DLOPEN=”

    LIBADD_POW=”

    LIBADD_SHL_LOAD=”

    LIBICONV=”

    LIBLTDL=”

    LIBOBJS=”

    LIBS=”

    LIBTOOL=”

    LIB_PREFIX=”

    LIB_VERSION=”

    LIPO=”

    LN_S=”

    LTDLDEPS=”

    LTDLINCL=”

    LTDLOPEN=”

    LTLIBOBJS=”

    LT_CONFIG_H=”

    LT_DLLOADERS=”

    LT_DLPREOPEN=”

    MAKEINFO=’${SHELL} /my_odbc_drivers/unixODBC-2.3.0/libltdl/config/missing –run makeinfo’

    MKDIR_P=’/bin/mkdir -p’

    MSQL_FALSE=”

    MSQL_TRUE=”

    NM=”

    NMEDIT=”

    OBJDUMP=”

    OBJEXT=”

    OTOOL64=”

    OTOOL=”

    PACKAGE=’unixODBC’

    PACKAGE_BUGREPORT=’nick@unixodbc.org

    PACKAGE_NAME=’unixODBC’

    PACKAGE_STRING=’unixODBC 2.3.0′

    PACKAGE_TARNAME=’unixodbc’

    PACKAGE_URL=”

    PACKAGE_VERSION=’2.3.0′

    PATH_SEPARATOR=’:’

    PREFIX=”

    PTH_CFLAGS=”

    PTH_CPPFLAGS=”

    PTH_LDFLAGS=”

    PTH_LIBS=”

    QNX_FALSE=”

    QNX_TRUE=”

    RANLIB=”

    READLINE=”

    SED=”

    SET_MAKE=”

    SHELL=’/bin/sh’

    SHLIBEXT=”

    STRIP=”

    SYSTEM_FILE_PATH=”

    SYSTEM_LIB_PATH=”

    VERSION=’2.3.0′

    WITHLT_FALSE=”

    WITHLT_TRUE=”

    YACC=’yacc’

    YFLAGS=”

    ac_ct_CC=”

    ac_ct_DUMPBIN=”

    am__EXEEXT_FALSE=”

    am__EXEEXT_TRUE=”

    am__fastdepCC_FALSE=”

    am__fastdepCC_TRUE=”

    am__include=’include’

    am__isrc=”

    am__leading_dot=’.’

    am__quote=”

    am__tar=’${AMTAR} chof – “$$tardir”‘

    am__untar=’${AMTAR} xf -‘

    bindir=’${exec_prefix}/bin’

    build=”

    build_alias=”

    build_cpu=”

    build_os=”

    build_vendor=”

    datadir=’${datarootdir}’

    datarootdir=’${prefix}/share’

    docdir=’${datarootdir}/doc/${PACKAGE_TARNAME}’

    dvidir=’${docdir}’

    exec_prefix=’NONE’

    host=”

    host_alias=”

    host_cpu=”

    host_os=”

    host_vendor=”

    htmldir=’${docdir}’

    includedir=’${prefix}/include’

    infodir=’${datarootdir}/info’

    install_sh=’${SHELL} /my_odbc_drivers/unixODBC-2.3.0/libltdl/config/install-sh’

    libdir=’${exec_prefix}/lib’

    libexecdir=’${exec_prefix}/libexec’

    localedir=’${datarootdir}/locale’

    localstatedir=’${prefix}/var’

    lt_ECHO=’echo’

    ltdl_LIBOBJS=”

    ltdl_LTLIBOBJS=”

    mandir=’${datarootdir}/man’

    mkdir_p=’/bin/mkdir -p’

    msql_headers=”

    msql_libraries=”

    oldincludedir=’/usr/include’

    pdfdir=’${docdir}’

    prefix=’NONE’

    program_transform_name=’s,x,x,’

    psdir=’${docdir}’

    sbindir=’${exec_prefix}/sbin’

    sharedstatedir=’${prefix}/com’

    subdirs=”

    sys_symbol_underscore=”

    sysconfdir=’${prefix}/etc’

    target_alias=”

    ## ———– ##

    ## confdefs.h. ##

    ## ———– ##

    /* confdefs.h */

    #define PACKAGE_NAME “unixODBC”

    #define PACKAGE_TARNAME “unixodbc”

    #define PACKAGE_VERSION “2.3.0”

    #define PACKAGE_STRING “unixODBC 2.3.0”

    #define PACKAGE_BUGREPORT “nick@unixodbc.org

    #define PACKAGE_URL “”

    #define PACKAGE “unixODBC”

    #define VERSION “2.3.0”

    configure: exit 1

    (0) 
    1. Ingo Hilgefort Post author

      Hello Sangeeta,

      this is a trial – which means that you can not connect it to systems outside the trial and you can not upload your own data. The trial allows you to leverage the pre-configured scenarios.

      All other usage scenarios are legally declined in the Terms and Conditions.

      regards

      Ingo Hilgefort, SAP

      (0) 
  10. Birute Grybauskiene

    Hello Ingo,

    I have activated HANA BW/BO instance in CAL, but I am not able to connect using remote desktop: remote desktop can’t connect to remote computer for one of these reasons…. . What could be the problem ? I terminated once and activated again – I am getting the same error. I mean Server/Frontend IP adresses are not reachable.

    Thanks,

    Birute

    (0) 
    1. Ingo Hilgefort Post author

      Hello Birute,

      are you trying to connect to the IP Addresses from your corporate network ? Could you try from a “free” internet connection ? It could very well be that – in case you trying to use it from a corporate network – those connections are blocked and that you need to be on a free internet connection.

      regards

      Ingo Hilgefort, SAP

      (0) 
      1. Birute Grybauskiene

        Thank you for answer. I will try to connect from “free internet connection”, but I thought about the same and tried to ping specified IP’s from internet sites and got “timed out”, so I am not sure that corporate network is the problem.

        (0) 

Leave a Reply