How to launch interactive application using Autosys?

[Anon Anon]

We've requirement to launch interactive application using Autosys agent.

 

Autosys job launch/start batch file. This batch file contain code to start UI application on server.

We can see in Task manager application started but we can't see it's UI.

 

This is because autosys starting application in Windows session ID 0. Which is windows services non-interactive session.

I'm logging to different session.

 

Is there way in autosys to force to start application other available session rather than Session 0 (zero)?

[Antony Askew]

This should already be in AutoSys - Did you try adding "interactive: y" to the job definiton?

[Anon Anon]

"interactive: y" worked, thanks Antony_Askew.

[Mark_Hanson]

More information (and caveats) for the interactive attribute can be found here.

[Anon Anon]

Thanks Mark, but the link is not working.

My issue is resolved after adding "interactive: y"

[Anon Anon]

after adding interactive: y, it is partially working having below issue.

when I keep logged in to the server that time it works.

But if I login to server and disconnect remote connection (Not logging off) that time job is failing with below error -

 

Wed Sep 28 10:49:28 2016 CAWA_E_20020 Logon failed for <Windows_ID> due to: Unable to locate interactive logon session.Error code: 20013

[Chandru.Venkataraman]

You can run jobs on session 0 (service session) instead of using terminal services client by setting the following parameter in the agentparm.txt

oscomponent.interactive.sessionzero=true

 

Read the caveat before using session 0

Workload Automation Agent Future Considerations - CA Technologies 

 

Cheers,

Chandru

[Anon Anon]

My aim is to run job interactively. I've some UI application which I want to launch using autosys job.
Therefore I want to run using below field but when I do so it works if session is active but if it is non active session then getting error as highlighted above.

interactive: y

[Chandru.Venkataraman]

Right, that is expected; to run an interactive job there needs to be (at the least) one session for that user (job owner), unless you setup the session 0 (oscomponent.interactive.sessionzero=true) as advised before.

With oscomponent.interactive.session.ignoreinactive=true set, the agent still needs a session, however it need not be an active (terminal services) session.

Note: The legacy AutoSys agent ran on session 0 by default.

[Anon Anon]

Can you please explain what exactly below settings is for?

oscomponent.interactive.sessionzero=true

 

On Server I want to run some jobs non-interactively i.e. in session zero

and one job interactively, will "oscomponent.interactive.sessionzero=true" impact all the jobs or only to jobs which have interactive: y ?

[Chandru.Venkataraman]

With oscomponent.interactive.sessionzero=true set, all "intertactive: y" jobs will be run in session 0.

Please read the following documentation on setting the Agent up to run interactive jobs on Windows:

Configure the Agent for Windows Interactive Jobs - CA Workload Automation Agents - 11.3 - CA Technologies Documentation 

[Anon Anon]

if I run interactive jobs in session zero then I'll not be able to login and view the launched UI. I guess windows doesn't allow to login to session zero.

[Chandru.Venkataraman]

You need to ensure the Interactive Services Detection Service is running to be able to step in and out of Session 0.

Please see this KB: http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec1441838.aspx

[Chandru.Venkataraman]

Set the following parameter in the Agent agentparm.txt file and restart the Agent service, and test the interactive job:

oscomponent.interactive.session.ignoreinactive=true

 

Cheers,

Chandru