PricingServerHostName specifies the IP address or the host name of the computer on which PDC is deployed Specifies the Oracle wallet that stores the sensitive information, such as database passwords, where BRMIntegrationPackWallet is the complete path to the Oracle wallet in BRM Integration Pack.Ĭontains details about the cross-reference database, where:ĬrossRefUserName specifies the cross-reference database user nameĬrossRefHostName specifies the IP address or the host name of the computer on which the cross-reference database is configuredĬrossRefPort specifies the port number assigned to the cross-reference databaseĬrossRefServiceName specifies the name of the cross-reference database serviceĬontains details about the PDC server, where:
The root element of SyncPDCConfiguration.xml. Table 3-1 Elements in the SyncPDCConfiguration.xml File Element See " Deleting Setup Components" for more information. If you delete a setup component (or any of its fields) from the billing or rating system, you must manually remove the corresponding PDC component (or its fields) from the PDC database.
See " Changing Display Names" for more information about updating PDC display names. If you later run SyncPDC to resynchronize this event, it retains the name change. For example, you can change EventTelcoGsmVoice to Voice Call. You can change the PDC display name in PDC. For example, it creates the GsmTelephony PDC name for the /service/gsm/telephony service name in BRM. When synchronizing setup components, SyncPDC creates display names in PDC for the corresponding data objects and their fields. See " Generating Synchronization Reports" for more information. It generates reports for the components that it synchronizes. SyncPDC synchronizes only the changes from the previous synchronization. SyncPDC synchronizes the following setup components:Īfter these setup components are synchronized with PDC, any modifications to these setup components must only be done in the system in which they were initially defined and then resynchronized. Ensure that / event/ realtimeDiscount does not exist in BRM during synchronization.
0 kommentar(er)
