ADF Ui Pages can be based on Webservice datacontrols to show the information fetched from webservices.
During Development the Ui might be based on services deployed in Developement server/Mock services running on tools like SOAP UI. When this UI moves to Integrated Test environment/Pre-Production Environment/Production Environment, the endpoints of the services used will change.

To make the UI work in all the environments, the endpoint URL's have to be changed based on the environment in which the UI is deployed.
(HERE I AM ASSUMING THAT THERE IS NO UDDI REGISTRY INVOLVED and this assumption is true in most of the client sites. If the UDDI registry is involved then there is nothing to change in the UI side. Everything will be maintained/changed only in the UDDI. If multiple UDDI registries are involved then again the url to the UDDI registry has to be changed in the UI.).

In ADF, the information about the service being invoked is present in the "connections.xml" file. This information includes things like the WSDL url, the endpoint etc. This information can be changed manually by changing the values of the following .

• Identify the "wsconnection" XML element that corresponds to the service being invoked.
• Change the "description" attribute of this element to point to appropriate WSDL url.
• Identify the "service"  XML element in the "wsconnection" element and within that element search for the element which looks like
  
  
  Change the "addressUrl" attribute so that it points to the appropriate endpoint.

That's it.
When you run the UI, it will start making calls to the new location instead of the old one.

Instead of changing this information manually, the above series of steps can be performend using an automated script (like ant/custom java /perl script) as well.

http://www.oracle.com/technetwork/developer-tools/adf/learnmore/index-101235.html
The above link contains a lot of links for common adf problems and their solutions.

http://www.oracle.com/technetwork/developer-tools/adf/queueactioneventinregion-155252.html
The above link shows how the parent page can programmatically control navigation inside a region.

http://blogs.oracle.com/groundside/entry/adventures_in_adf_logging_part
The above link contains information about ADF logger.

http://niallcblogs.blogspot.com/2011/12/bpm-11g-feature-pack-update-task.html
This link contains important bpm 11g related blogs

The following are some of the things that needs to be remembered when using  remote taskflows.

• Remote taskflow activities can only invoke remote bounded taskflows with JSPX pages.
• Remote taskflow activities cannot be used in the taskflows with page fragments.
• The only way to use the remote taskflows inside a page fragment is by having inline frames in the page fragment and point it to a local taskflow with JSPX pages having the remote taskflow activity. The communication between the content of the iniline frame and the parent page/pageFragement can be done using java script.
• The calling taskflow does not propagate the security information to the remote taskflow if the remote taskflow is running in a different server.