Having already installed Customer Hub PIP 2.5 and Order To Cash PIP 2.5 with Siebel UCM & CRM instance say UCM-A and CRM-A. After the install, we planned to change the end points from UCM-A to UCM-B and also from CRM-A to CRM-B. What are the steps/procedure to make the changes required?
It is not feasible to link up the same UCM env to 2 Middleware environments without issues. The UCM outbound services can be configured to publish events to only 1 Middleware environment at any given time. So the outbound flows can point to only one PIP installation. If you intends to use both installations together, then outbound events won't happen on both Middleware environments, only one. If you are going to use it in turns, then that might work.
Question
We need to remove a cycle forward event from existing product which is being used for both the prepaid and postpaid customers. We don't want the pin_cycle_forward to pick up prepaid accounts.
You have AIA deployed on one server, BRM is on the same network. Siebel on the other hand is installed on a server which is behind a firewall.
Which ports on the firewall need to be opened from SOA Suite and Siebel networks in order for the integration to work?
There are 2 considerations when having a firewall between Siebel and the SOA Suite used by AIA:
1- All the AIA ABCs providers which connect from SOA Suite to Siebel invoke a Web Service in Siebel.
It works in the following way: within the Siebel workflow, there is a step (Marketing Campaign Load Workflow>Get List Format System Data) that takes the body of the HTML and finds all the tags Trackable URL.The business service replaces that tag with a long URL that includes the target page concatenated with a bunch of internal IDs (see example below)
It is possible to set up locales on a user basis so that you do not need to create new object manager components in order for a set of users to simply use a different locale. A locale directs how sensitive information, such as date, time, and numbers are shown and may be different from country to country.
Lets explore few basic troubleshooting steps required during performance issues related to CheckIn / CheckOut process using Siebel Tools.
1. Check if this problem is happening on all machines or single machine. Also check whether the all developers are affected or single developer. This step helps in isolating the root cause of the performance problem.
The only supported way in which you can delete a repository is by way of deleting the appropriate ‘Repository’ record within the Siebel Tools application. By doing this it will perform a cascade delete on all the child objects associated to the Repository object.
To delete a Siebel Repository:
Limitations :
