PowerServer 2022 R2 Help
Work with the PowerServer C# solution

"Applications": This block includes a list of the deployed applications and the mappings of transactions and connection caches, timeout values for transaction, session, and request, and run mode (0-normal mode, 1-test mode) of each deployed application.

Take the following settings for example, in the "salesdemo_cloud" application, the "sqlca" transaction object is mapped to the "sales" database cache. Refer to Managing transaction-to-cache mappings in PowerServer for more information.

To understand and set appropriate timeout values for "Transaction", "Session" and "Request", refer to Configure the timeout settings.

You can run the application in test mode ("RunMode": 1) if you want to perform load-testing for the application. For more, refer to Tutorial: Load testing installable cloud apps.

The MaxSPCache setting specifies the maximum number of stored procedures for which the driver caches information. The driver retrieves information from the server about a stored procedure's parameters the first time the stored procedure is called and caches that information. The next time the procedure is called, the driver retrieves the information from the cache to improve performance. The information is retrieved based on the stored procedure's name. The name is case sensitive. If you call two different stored procedures with the same name, you can turn off caching by setting the value of MaxSPCache to 0.

  "Applications": {
    "salesdemo_cloud": {
      "CloudTransactions": {
        "sqlca": {
          "CacheName": "sales"
        }
      },
      "Transaction": {
        "Timeout": 120,
        "TransactionException": true
      },
      "Session": {
        "Timeout": 3600
      },
      "Request": {
        "Timeout": 3600
      },
      "RunMode": 0,
      "MaxSPCache": 50
    }
  },

"Connections": This block includes a list of the cache groups and caches. Refer to Managing database caches in PowerServer for more information.

  "Connections": {
    "Default": {
      "local-sa": {
        "ConnectionType": "Odbc",
        "OdbcName": "PB Demo DB V2022R2",
        "OdbcDriver": "SqlAnywhere",
        "UserID": "dba",
        "Password": "eyJQYX...",
        "CommandTimeout": 30,
        "SecurityOptions": null,
        "OtherOptions": null,
        "DynamicConnection": false       
      }
    }
  }

"LicenseKey" & "LicenseCode": PowerServer license information. Refer to Importing the PowerServer license for more information.

"EncryptedSensitiveData": Sensitive data refers to the database login password which is used to create the database connection cache in Applications.json. If the password is an encrypted value (encrypted automatically by IDE or manually by the CustomizeDeploy.dll tool), this setting should be set to True; if the password is not encrypted (still a plain-text string), this setting should be set to False so that PowerServer will encrypt the password for you and store the encrypted value to the database. If this setting is set to True and you input a plain-text password, the plain-text password will be directly stored to the database.

"ProxyOptions": The IP address and login credentials of the proxy server. If the Web API host server connects to Internet through a proxy server, you will need to configure the proxy server settings here. The password for the proxy server must be an encrypted value (encrypted by the CustomizeDeploy.dll tool).

"EmailOptions": This block must be configured first if you want to get notifications for license expiration. The settings include the SMTP server settings, sender email settings, and recipients. Refer to Configuring the email settings for more information.

"StatisticsOptions": This block determines which type of transaction statistics will be generated and cached in the memory. Some settings are disabled by default to lower memory usages. You can also take advantage of the StatisticsController APIs in PowerServer to get the statistics.