The purpose of setting up the mapping is to make sure the configured data source can access the database server for the Appeon Web or mobile application as the replacement of the transaction object in the PowerBuilder application.
Once PowerServer data sources are configured, you can set up the transaction object to data source mapping in two different ways:
-
Higher priority: Dynamic transaction object to data source mapping via PowerScript.
-
Lower priority: Static transaction object to data source mapping in AEM. The mapping in PowerScript has priority over the static mapping in AEM.
Dynamic mapping is of higher priority, meaning that if a transaction object named "SQLCA" is both mapped to data source A via PowerScript and mapped to data source B in AEM, the transaction in effect is mapped to data source A.
Note that if PowerServer is installed to WebLogic, WebSphere, JBoss, NetWeaver Application Server, or JEUS, PowerServer and AEM reads data source JNDI names as data source names.
