SAP as fast as

The introduction of SAP, in the ordinary world, is not considered to be the simplest task. Various analysts, according to a special methodology, are examined, shoveled the whole enterprise, change business processes, consult a lot and once again, and even the IT infrastructure is calculated by specially trained super specialists. However, to help us, there is a service for the automated deployment of German products in the mode: clicked, waited, test (or even work).
SAP as fast as

This service is called the SAP CAL (Cloud Appliance Library).
If you want to see the functionality of something "sapper", then you only need to have resources in one of the big clouds (Azure, AWS, Google). Further, inside this library there are already preconfigured templates for a fairly large number of products.

The other day, I just had such a task, to cook one of the previously unknown products for me to show, I'm friends with Azure, then of course that's where I looked.
Further all is absolutely simple.
Choose a product, in my case it's SAP Solution Manager and get all available options for deployment:

Choose the option that is interesting and enter it:

We download various docks on the links and do not bother with painstaking reading, we immediately begin to deploy.
You will first need to link the SAP CAL account with an account in the existing Azure subscription (we also remember that you have it). In the corresponding account management dialog (in the upper left in the SAP Cal there is the Accounts menu), specify the name and password for Azure and the subscription ID. Azure subscription parameters are easily extracted, for example, by logging into portal into the subscriptions section.
Next, you will be offered a choice of two options: basic and advanced.
The base version is needed if you want to do everything as quickly as possible. In the expanded, it is possible to select the address space, the size of virtual machines, the size of the connected disks.
In both cases, it should be during the dialogue, set up a schedule in which the machines will automatically turn off (and if it is necessary to turn on), which will save quite decently.

Having chosen the option, we proceed to save the private key, which may be required to administer future servers. The key can be saved locally or in the built-in SAP CAL (choose depending on the level of built-in sense of paranoia).

After the warning (for a free trial version) that the installation is deployed for the "demo" and do not follow the performance measure, etc. the automated deployment of the product begins.
In fact, that's all. It remains only a long time to wait. For simple deployments, for example, a single-machine version of SAP S4 /HANA is about 40 minutes. For larger versions, for example, for a five-machine implementation of Solution Manager + SAP S4 /HANA, the deployment time was about 4.5 hours.

We receive a summary of the detailed resources:


After deployment, in addition to productive servers, a jump node is automatically created, which can be accessed from the public IP address via RDP, and further, through it productive servers are administered (which are not visible from the outside).

Or you can start here to see the product itself, in our case Solution Manager:

What did not like.
Although the service informs about the planned cost of resources, I would still like to know exactly what we'll get as a result. The target ARM template before deployment can not be pulled out, and the descriptive document that is present does not reveal the essence of the implementation in a particular cloud. Uncomfortable. Could and immediately share the template. Not like pulling ARM template after deployment.
At the same time, there are also products left behind which, although they are in the library, are designed for deployment without a trial period, immediately for real money. In this case, to see what infrastructure will be deployed the more it will not work.
But in general, for most of the products presented in the library, you can deploy without getting into the subtlety of the infrastructure and immediately begin functional testing.
What actually was required.
+ 0 -

Add comment