Hi Thomas,

I wrote a workflow solution to this problem some time ago, and it still seems 
to work (Just tried it on 9.1.3)

It is basically one form with 2 escalations.

The following information is recorded in the form


  *   User Login Name
  *   License Name (AR User, Change , Incident … etc)
  *   License Type (Fixed, Floating, Read)
  *   Server Name (Server the user is logged into)
  *   Time Acquired (Time the license was acquired)
  *   Duration (How long the user has used the license (In Seconds))
  *   Status (Currently logged in or logged out)

More than happy to share this if it suites your needs.

Kind regards
Jacques Andre



From: ARSList <[email protected]> On Behalf Of Theo Fondse
Sent: 23 August 2019 10:11
To: 'ARSList' <[email protected]>
Subject: RE: How to run a job on individual servers?

Hi Thomas,

Conny has a very good idea. If your organization’s security policies allow for 
it, it will work just fine.

If you wanted / were forced to use a more old-school AR System-based approach, 
you will need to create two dummy forms populated with a record for each server 
in the group and then trigger something like the driver program or arimport 
from a run process triggered by an escalation on Dummy Form 1.
The driver/arimport then does a login to the individual server in the group and 
modify the record for that server on Dummy Form 2.
This can then trigger workflow to execute locally on the intended server in the 
group to do what you want on that specific server.

See 
https://docs.bmc.com/docs/ars91/en/enabling-the-data-import-utility-609071980.html
 for info on running arimport (much easier than doing this with the driver 
program).


Best Regards,

Theo Fondse

From: ARSList [mailto:[email protected]] On Behalf Of 
[email protected]<mailto:[email protected]>
Sent: Wednesday, 21 August, 2019 02:11 PM
To: [email protected]<mailto:[email protected]>
Subject: AW: How to run a job on individual servers?

I would not recommend to run arsystem as root (from a security point of view) 
For ssh you can use whatever user you like, which has sufficient permissions to 
run your “licensetracker”. You’ll have to make sure, that the user running 
arsystem is able to do ssh to the target servers/user without the need of any 
password. (Public-Key Authentication)

KR Conny
Von: ARSList <[email protected]<mailto:[email protected]>> 
Im Auftrag von Thomas Miskiewicz
Gesendet: Mittwoch, 21. August 2019 14:03
An: ARSList <[email protected]<mailto:[email protected]>>
Betreff: Re: How to run a job on individual servers?

Fabulous idea. As which use shall I do the ssh? The system is running as root

On Wed 21. Aug 2019 at 13:46, 
<[email protected]<mailto:[email protected]>> wrote:
Hi,

if you're on *x, you can do something like

RUN-PROCESS ssh server1 /path/to/your/licensetracker
RUN-PROCESS ssh server2 /path/to/your/licensetracker
RUN-PROCESS ssh server3 /path/to/your/licensetracker

within an escalation. If escalations are running on server1 it will connect via 
ssh to itself, which does not really matter.

KR Conny

-----Ursprüngliche Nachricht-----
Von: ARSList <[email protected]<mailto:[email protected]>> 
Im Auftrag von Thomas Miskiewicz
Gesendet: Mittwoch, 21. August 2019 13:21
An: ARSList <[email protected]<mailto:[email protected]>>
Betreff: Re: How to run a job on individual servers?

We're collecting license information on each individual server reading the 
user.log I’m looking for a way to trigger the action on each individual server 
without having to use a cron job.

> On 21. Aug 2019, at 13:18, Tauf Chowdhury 
> <[email protected]<mailto:[email protected]>> wrote:
>
> Do you mean escalations? Also is this during a maintenance period or 
> scheduled outage? You could always bring up one server at a time and that way 
> you can ensure escalations are running on that server if you’re in a server 
> group with the failover configured.
>
> Sent from my iPhone
>
>> On Aug 21, 2019, at 6:50 AM, Thomas Miskiewicz 
>> <[email protected]<mailto:[email protected]>> wrote:
>>
>> Hi there
>>
>> we got three servers in the group and would like to collect information on 
>> every individual server. We did that in the past using a cron job but would 
>> prefer escalation which can be controlled by workflow. The problem is 
>> explanations run only on one of the three servers. Any idea how to trigger 
>> workflow on each individual server?
>>
>>
>> Thomas
>> --
>> ARSList mailing list
>> [email protected]<mailto:[email protected]>
>> https://mailman.rrr.se/cgi/listinfo/arslist
>
> --
> ARSList mailing list
> [email protected]<mailto:[email protected]>
> https://mailman.rrr.se/cgi/listinfo/arslist


--
ARSList mailing list
[email protected]<mailto:[email protected]>
https://mailman.rrr.se/cgi/listinfo/arslist

--
ARSList mailing list
[email protected]<mailto:[email protected]>
https://mailman.rrr.se/cgi/listinfo/arslist
This communication is the property of CenturyLink and may contain confidential 
or privileged information. Unauthorized use of this communication is strictly 
prohibited and may be unlawful. If you have received this communication in 
error, please immediately notify the sender by reply e-mail and destroy all 
copies of the communication and any attachments.
-- 
ARSList mailing list
[email protected]
https://mailman.rrr.se/cgi/listinfo/arslist

Reply via email to