Server Tables Cleanup component failing - deadlock trying to delete records from s_srm_request

"In Siebel version 7.7, the SRProc component has a new parameter called Enable Various Housekeeping Tasks (Parameter alias = EnableHouseKeeping). This parameter is similar to the previous parameter in Siebel version 7.5.x and earlier called DeleteOldReqs. You should leave the default value of False for the EnableHouseKeeping parameter alias, otherwise both the SRProc and ServerTableCleanup components will try to clean up the same tables and cause potential deadlock type behaviors."

Can 2 Middleware environments share the same Siebel UCM 8.1.1 environment using the customer MDM PIP?

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.

Firewall Considerations when Siebel is behind a firewall

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.

Recent content