cancel
Showing results for 
Search instead for 
Did you mean: 

Passing user input to a custom operation in LVM

former_member487627
Discoverer
0 Kudos

Hello Everyone,

I'm trying to find out if this is even possible and if anyone has a current solution in LVM?


I have a custom operation in LVM that will stop SAP and my DB instance then take a

DB backup. Is there a way to prompt for user input that will be

passed along to the operation. For example when I initiate my operation

I'd like to be prompted for Backup retention (30, 60, 90) days and

some type of related comment. These values then get passed along to the

operation to perform the backup and log the comment accordingly.

I thought that using a confirmation action and the parameter supplier

might be an option but I can't seem to put the pieces together. I tried to reference SAP Note: 1936615 parameter supplier dynamic values but it is not released for viewing.


Has anyone figured out a way to do this?

Also, I'm running LVM 2.1.2



I look forward to seeing what the community thinks?



Thank you,


Sean Nelson

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello Sean,

this is possible via customer defined parameters.

You can find this in the provider implementation as an option.

You can define a variable e.g SID, a value for it is then asked when the custom operation is executed. The value can be passed to your skript via a definition in your xxx.conf file, e.g.

Name: echo

Description: Test

Command: /tmp/echo.sh  $[PARAM-SID:#required]

Hope this helps.

Best Regards,

Andreas

former_member487627
Discoverer
0 Kudos

Thanks Andreas,

I poked around with this a bit and was able to get my desired results.

I ended up using dynamic values using a drop down list. and a custom string entry field.

Do you know if there's a way to implement these user selected values during the creation of a mass task? For example I create my mass task and it prompts me to input the required values ahead of time. These would then run against all instances in the task. Currently, this fails as it wants user input for these mandatory fields.

Thanks,

Sean Nelson

Former Member
0 Kudos

Hi Sean,

sorry for my late response.

Unfortunately I don't get what you want to achieve... can you give another example?

BR,

Andreas

Answers (0)