Job Management – Mass Scheduling tool

You use the Job Management functionality in SAP Solution Manager, i.e. you document your jobs and schedule them centrally from Solution Manager. Now you had a change in your organization and need to change the owner of a set of jobs or you have a new project, which makes a set of jobs obsolete and requires a new set of jobs to be scheduled at go live. To do the needed changes you would need to do them one by one, accessing the corresponding JD. You would like to have a tool that helps you to mass change and mass schedule / De-schedule them!

The Mass Scheduling tool is used to schedule jobs for the mass volume of Job Documentations. This supports scheduling jobs using XBP and SMSE Interfaces. To get started of using this amazing tools please follow up:

Please enter the Job Documentation ID or you could click on the icon to select multiple jobs documentation. Also, enter the System and Client information of the managed system.

Here are the results:

The Job Scheduled already would be indicated with Green color.

Now, you could select single or multiple job(s) then simply click on “Schedule Job(s)” to schedule them or “Delete Job(s)” to De-Schedule them. These two options would be indicated with the status and the status description.

If you would like to see the scheduling information in the web UI, please click on the ID of the desired job.

The input criteria can be left blank in order to list all the job documentations per system:

The mass scheduling report RAGS_JSM_MASS_SCHEDULE is available on SP07.

Central Source of information: https://wiki.scn.sap.com/wiki/display/SM/Job+Management

  http://bit.ly/2FQMhp4 #SAP #SAPCloud #AI

Troubleshooting connection problems: HANA express from HANA Studio

After repeatedly seeing questions around failed connections to HANA Express, I’m compiling the basic troubleshooting steps I take when, for example, HANA Studio does not connect to my HXE instance. The most typical error is:

The system cannot be reached. logon data cannot be used.

The order in the steps is not random. If any of the tests fail, moving forward with the next step does not make any sense without fixing whatever is causing the test to fail.

Is the database running?

Sounds obvious but worth checking.

From the console in your server, you can use ./HDB info and make sure you can actually connect  using hdbsql -i -d Properties–>JDBC trace:

Options for other clients can be found in the help.

Further help, as usual, can be found in the Q&A. Be sure to search for your question before you post it and add all the information you consider relevant (what error you are getting, what have you already tried and failed, some screenshots).

  http://bit.ly/2HHh6wP #SAP #SAPCloud #AI

DocFX: The Next Documentation Tool to Consider?

ICYMI: I recently started some documentation work for a project written in C#, and after researching tooling for auto-generating docs from the code base and falling down a rabbit hole, I emerged from the other side and found DocFX. Microsoft owns the project, but I think they rescued it from an abandoned project at some point. While it has a lot of features well suited to C# code bases, I also unearthed a plethora of other fantastic documentation features to suit projects written in any language.

DocFX Flavored Markdown (DFM)

Bringing yet another flavor to the sometimes too simple Markdown, DFM includes all GitHub Flavored Markdown syntax and adds a lot of syntaxes specific to using DocFX to build your documentation. Some of the syntax is so useful and pleasant to use, I hope other platforms adopt it. This isn’t a comprehensive list, but here’s what I’ve found most helpful so far. You can find a full list on their website, but not all in one place. https://goo.gl/C7QLiL #DataIntegration #ML

Rules for Extending Your API With Each Version

I’m spending time learning from the API design guides of other leading API providers, absorbing their healthy practices, and assimilating them into my own consulting and storytelling. One API design guide I am learning a lot from is out of the Adidas Group, which contains a wealth of wisdom regarding not just the design of your API, but also the deployment and evolution of the API resources we are publishing.

One particularly interesting piece of advice I found within Adidas API design guidance were their rules for extending an API, which I think is pretty healthy advice for an API developer to think about. https://goo.gl/WTw19N #DataIntegration #ML