Dear all, We have the following problem. There is an Appian infrastru

Dear all,

We have the following problem. There is an Appian infrastructure that is already installed and users of an organization have access to (green). In this infrastructure we already have some Appian applications deployed (green). We want to develop a new Appian Application (orange), and give access to that application to external (and internal) users. One solution we thought would be to setup a new infrastructure (red) that includes an HTTP server and an Appian AS (running tempo) and to put this in different zones in our network configuration. This will ensure that we will only open up Tempo to external users.
Using access right configuration on Tempo we can make sure that the new external users will be able to only access the new application we will develop. The problem is that (in this way) we also allow internal users to access this application (and other applications) externally. If the internal users use their internal credentials to ac...

OriginalPostID-172560

OriginalPostID-172560

  Discussion posts and replies are publicly visible

Parents
  • This is not possible. Each app server's unattended poller will poll the engine's work queue and pick up items as they become available, so there is no guarantee which app server will do which work (user's session does not matter for unattended activities). That said the data will be stored temporarily only in the app server's heap until it is discarded, garbage collected or the app server restarted.
Reply
  • This is not possible. Each app server's unattended poller will poll the engine's work queue and pick up items as they become available, so there is no guarantee which app server will do which work (user's session does not matter for unattended activities). That said the data will be stored temporarily only in the app server's heap until it is discarded, garbage collected or the app server restarted.
Children
No Data