Is there a way for a process model to obtain information about the server Appian

Is there a way for a process model to obtain information about the server Appian is running on? Server name, install directory, JVM parameters, environment variables, etc.?...

OriginalPostID-109474

OriginalPostID-109474

  Discussion posts and replies are publicly visible

Parents
  • We're trying to be creative about a problem we have with our Disaster Recovery (DR) Strategy. We have set up a separate DR environment with separate servers that have live replication of the Production data getting fed to them so that whenever a failover needs to occur, we won't have any data loss (Mike, you'll be familiar this since you helped me set it up). The problem with this is that some of the process models currently in Production point to Production Web Services (using a hardcoded WSDL). So when we failover to the DR servers and pick back up with the replicated data, the process model is still pointing to the Prod WSDL (which, in a real DR scenario, won't be available because the web service is internally hosted so it would need to failed over to DR as well). So we need a way to make the process aware of what environment it is running in so it can use the correct WSDL. We've considered just setting up a Constant that says what environment it is, but that would have to be manually changed from "PROD" to "DR" as soon as the failover occurs, which isn't ideal.
Reply
  • We're trying to be creative about a problem we have with our Disaster Recovery (DR) Strategy. We have set up a separate DR environment with separate servers that have live replication of the Production data getting fed to them so that whenever a failover needs to occur, we won't have any data loss (Mike, you'll be familiar this since you helped me set it up). The problem with this is that some of the process models currently in Production point to Production Web Services (using a hardcoded WSDL). So when we failover to the DR servers and pick back up with the replicated data, the process model is still pointing to the Prod WSDL (which, in a real DR scenario, won't be available because the web service is internally hosted so it would need to failed over to DR as well). So we need a way to make the process aware of what environment it is running in so it can use the correct WSDL. We've considered just setting up a Constant that says what environment it is, but that would have to be manually changed from "PROD" to "DR" as soon as the failover occurs, which isn't ideal.
Children
No Data