Application Environments
Each cloud service by default comes with three environments designated as Development, Test, and Production. Test and Production are sized as full-sized environments based on the billable metric of the subscription, while Development is a smaller environment.
Customers can request additional non-production environments through the initial sales order or in a subsequent order for an additional subscription. When asking for more environments, the names of the base and additional environment are predefined and cannot be changed.
Environment Names and Codes
Cloud service environments have an environment code and name. The environment code is used to identify the environment and enable migration processes (such as configuration migrations) between the environments. The environment code is also used at installation/provisioning time. The table below lists all the possible environments that can be provisioned for each cloud service.
Environment Code
Name
Type
Default
Additional
DEV
Development
Development
Yes
No
TEST
Test
Test
Yes
No
PROD
Production
Production
Yes
No
DEV01..DEV20
Development 1 .. 20
Development
No
Yes
TEST01..TEST20
Test 1 .. 20
Test
No
Yes
Application / Environment Access and URL Tokens
When environment provisioning is complete, customers / implementers will receive a list of links to the various product environments included with their subscription. There are cases in which cloud service applications need to access other cloud service or on-premises applications or other environments, such as:
• Data/Configuration Migration
• Data Conversion
• Redirecting a user to another application as part of a business process transaction that is integrated across products
• Invoking web services of a different application (another cloud service or SOA for existing SOA-supported cloud integrations)
• Invoking a web service of the same application in a different environment. This type of communication is used to help automate inter-environment processes like configuration migrations. See the Code and Configuration Migration section in Chapter 7: Operational Guidelines for more information.
The following URL Tokens are available for direct navigation or web service calls for each cloud service.
Token
Description
EXT_PUB
Prefix token that should be used to reference external addresses in Message Senders.
 
For example, to reference paymentcorp.payusa.com endpoint URL you would need to use the following notation: @EXT_PUB@paymentcorp.payusa.com.
 
Note: The target URL must be on the allowlist.
CCS_WS
CCS_ONLINE
Customer Cloud Service address for web service calls.
Customer Cloud Service address for online access.
MSCS_WS
MSCS_ONLINE
Meter Solution Cloud Service address for web service calls.
Meter Solution Cloud Service address for online access.
WACS_WS
WACS_ONLINE
Work and Asset Cloud Service address for web service calls.
Work and Asset Cloud Service address for online access.
AICS_ONLINE
Analytics Insights Cloud Service (aka DataRaker) address for online access.
INT_WS
Invoke SOA web services (for integration via SOA)
BI_PUBLISHER_ADMIN
Analytics Publisher address for web services calls.
BI_PUBLISHER_ADMIN_INT
Used with Reporting Options with Analytics Publisher as "Reporting Server From App Server" for Batch reporting.
BIP_DEF_DIR
Used as soft parameter value ("Output Directory") to Analytics Publisher extract algorithm type.
BIP_DEF_PATH
Used as soft parameter value ("Report Absoluted Path") to Analytics Publisher extract algorithm type.
DEV_WS, DEV01_WS-DEV10_WS
TEST_WS, TEST01_WS-TEST10_WS
PROD_WS
Web service addresses for all possible environments.
For example, DEV_WS can point to Customer Cloud Service in the DEV domain while PROD_WS will point to the same application but in the PROD domain.
Usage Examples:
• The outbound message sender on the Customer Cloud Service configured for invoking a Meter Solution Cloud Service Inbound Web Service service named "ABC" (in production) will be have the URL definition of @MSCS_WS@abc.
• The value of @MSCS_WS@ will be different in each environment so that the same token can be used in all environments, and the runtime value translation will be based on the environment invoking the call.
• Internal-facing tokens such as DEV_WS can be used for inter-domain communications, such as the automation of configuration migration between product domains. These tokens are used by the Process Automation Tool within Cloud Service Foundation.
• External facing addresses will use the @EXT_PUB@ prefix, for example: @EXT_PUB@paymentcorp.payusa.com/api/int01/addPayment
• The port is not required in the URL definition when using EXT_PUB as all outbound calls from cloud services are sent via Https and port 443 is implied.