cancel
Showing results for 
Search instead for 
Did you mean: 

Auto start Network Connect with JSAM/WSAM

SOLVED
icebun007_
Contributor

Auto start Network Connect with JSAM/WSAM

Hi guys,

Is it possible to autostart Network Connect whilst using JSAM or WSAM at the same time?

I know that Network Connect will run automatically on its own after login to the IVE.

This fails if either the WSAM or JSAM is configured on another role at the same time. What happens is that the SAM will run instead and the Network Connect has to be started manually.

Is there a workaround?

Thanks.

1 ACCEPTED SOLUTION

Accepted Solutions
muttbarker_
Valued Contributor

Re: Auto start Network Connect with JSAM/WSAM

The actual behavior is quite interesting. If you setup NC and SAM (either JSAM or WSAM) to auto launch then the browser session simply ignores the NC and launches the appropriate SAM session. If you then attempt to manually launch NC you see two different actions.

With WSAM running the NC launch will prompt you to allow it to stop the WSAM session prior to NC launching. You can't start NC w/WSAM running. However, ff you choose to you can then restart WSAM and the two will coexist on the desktop.

Under JSAM the NC launch simply occurs and the JSAM session is left alone and JSAM and NC coexist.

Interestingly enough the JSAM rules seem to take precedence over the NC rules. I have a JSAM rule that is setup for MS Outlook and it does not work (due to port issues) with Outlook 2003. When I enable NC while JSAM is still running the Outlook connection still fails so based on that I would say JSAM is "on top."

View solution in original post

2 REPLIES 2
firewall72_
Frequent Contributor

Re: Auto start Network Connect with JSAM/WSAM

Hi,

I don't think so. I opened a ticket with JTAC early this year and they said NC and W/JSAM can't run at the same time. We have since remove the auto launch for NC on roles that require W/JSAM. This has worked out well.

Rgds,

John

muttbarker_
Valued Contributor

Re: Auto start Network Connect with JSAM/WSAM

The actual behavior is quite interesting. If you setup NC and SAM (either JSAM or WSAM) to auto launch then the browser session simply ignores the NC and launches the appropriate SAM session. If you then attempt to manually launch NC you see two different actions.

With WSAM running the NC launch will prompt you to allow it to stop the WSAM session prior to NC launching. You can't start NC w/WSAM running. However, ff you choose to you can then restart WSAM and the two will coexist on the desktop.

Under JSAM the NC launch simply occurs and the JSAM session is left alone and JSAM and NC coexist.

Interestingly enough the JSAM rules seem to take precedence over the NC rules. I have a JSAM rule that is setup for MS Outlook and it does not work (due to port issues) with Outlook 2003. When I enable NC while JSAM is still running the Outlook connection still fails so based on that I would say JSAM is "on top."