In SAP HANA Studio SPS07 there is a new function called “Add System Archive Link…”.

SystemArchiveLink_01.png

This function allows linking your SAP HANA Studio to a centrally stored SAP HANA Systems Archive file. The SAP HANA System Administrator only needs to maintain this central file once. All the linked SAP HANA Studios will display the SAP HANA Systems maintained in this central file.

Configuring SAP HANA Studio using “System Archive Link”

Maintain all SAP HANA System centrally on your central SAP HANA Studio. Don’t use the studio on you own laptop as a central studio, this because as a system administrator you might have SAP HANA systems in your list that shouldn’t be distributed to other people yet. I use the SAP HANA Studio on the SAP HANA Server, because it is available and it is central for all the studios in you companies network.

After you have maintained the system landscape in the central studio you need to export it. In SAP HANA Studio goto File -> Export. In the pop-up windows select SAP HANA => Landscape.

SystemArchiveLink_02.png

In the next screen (shown below) you can select which systems should be exported and you can select the location where the landscape.xml needs to be stored. Click Finish to export the landscape.xml.

SystemArchiveLink_03.png

Copy the landscape.xml file to a location that can be shared with all SAP HANA Studios.


Link the non-central SAP HANA Studio to the central landscape.xml file


Now the landscape.xml file is on a central place I start my local SAP HANA Studio. In the Systems view I open the context menu and select “Add System Archive Link…”.

SystemArchiveLink_05.png

In the pop-up fill in the field as shown below.

SystemArchiveLink_04.png

Click Finish to complete the action. In my local SAP HANA Studio I see now the system landscape that I exported from the central studio. The little chain icon shows that this is a linked system landscape.

SystemArchiveLink_06.png

This feature makes my life as SAP HANA System Administrator a bit easier, but exporting the system landscape every time I changed something in my setup is to much work.

Making it all even more easier

I think this whole setup can be done without exporting the landscape.xml file from the central studio every time I have changed the landscape. So I took a look at the central studio and found that the SAP HANA Studio stores it’s system landscape in the file hdbstudio.xml located in the directory <workspace>/.metadata/.plugins/com.sap.ndb.studio.datamodel

It is also possible to start SAP HANA Studio with different workspaces using the -data <new workspace location> argument on the command line. With this knowledge I setup a new workspace in the shared /hana file system on my server. I call this the SharedWorkspace.

As of now I start my central SAP HANA Studio with the command /hana/shared/HAY/hdbstudio/hdbstudio -data /hana/SharedWorkspace/ to make sure that the file hdbstudio.xml is on my shared /hana file system.

On my Linux Mint laptop I use the “add System Archive Link..” and linked to the file /hana/SharedWorkspace/.metadata/.plugins/com.sap.ndb.studio.datamodel/hdbstudio.xml Using the System Archive Link function to link to the always up to date central hdbstudio.xml makes sure that I don’t need to export the landscape.xml file anymore. Every time I start my local SAP HANA Studio it automatically pickup the changes from the central setup in the hdbstudio.xml file. Now my life really easier!

To wrap up thing

This worked for me in my test landscape, but your mileage may vary depending on your local SAP HANA System landscape and the security settings on the use of nfs between systems. I hope this also helps to make your life, as a SAP HANA System Administrator, a bit easier.

To report this post you need to login first.

9 Comments

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

  1. Lars Breddemann

    Hi Hay 🙂

    Nice blog and nice to see that for your use case also the approach of sharing the workspace works. A bit of caution is advised here, if one tries to use the shared workspace simultaneously from multiple computers… (read: this won’t work).

    The Archive link feature also has another nice aspect: you can integrate as many shared landscape.xml files as you like and you can place them where ever you want in your local Systems tree.

    That way it’s not necessary to have one big system landscape tree, but smaller ones that can be added to the local HANA studio on request.


    Thanks again for sharing your experience!


    – Lars

    (0) 
    1. Henricus Bouten Post author

      Hi Lars, Thanks for your feedback.

      Maybe the name SharedWorkspace makes it a bit confusing, but I’m not sharing workspaces.

      I put the workspace of my central SAP HANA Studio on a shared location hence the name SharedWorkspace. In that workspace only my central SAP HANA Studio does it thing. No other local SAP HANA Studio uses this workspace.

      The local SAP HANA Studios all have their own local workspace. The local SAP HANA Studios do a Archive Link to the hdbstudio.xml file inside the SharedWorkspace, but they don’t use that location as their workspace.

      The Archive Link on the local SAP HANA Studios uses the file hdbstudio.xml readonly. Hay

      (0) 
      1. Jan Goedtke

        Hi,

        sorry for being unclear 😉

        Normally I have to add the link manually by going through the menu.

        Can I add it automatically? We want to spread it through the company with as Little Manual activities as possible.

        In sapgui e.g. I can use a script for entering the path to saplogon.ini  …

        Jan

        (0) 
  2. Ralf Nellessen

    Hi,

    I tested this – thanks for the hint.

    We would like to distribute the details somehow it to a bigger community including end-users.

    And the SystemArchiveLink doesn’t solve my core issue when distributing the landscape.xml: User Names

    Problem: User names are sort of “baked in”.

    That’s no problem if you just access the HANAs using the SYSTEM username, also no problem if you use (simple) SSO.

    But as soon as you have user-specific entries (like an explicit “end” user name or the additional JDBC parameter user=… in the SSO case), then everybody’s landscape.xml is different and there is no way to distribute it. Correct?

    Did you already solve that part or am I just to stupid to see the solution?

    Best regards,

    Ralf

    (0) 
    1. Henricus Bouten Post author

      Hi Ralf,

      The “System Archive Link” has indeed the user name “baked” in the xml file. I also haven’t found a way yet to use it without the user name in the xml.

      I didn’t yet check in SPS10 is there is a change with this feature.

      — Hay

      (0) 

Leave a Reply