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.
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.
The above link contains a lot of links for common adf problems and their solutions.
The above link shows how the parent page can programmatically control navigation inside a region.
The above link contains information about ADF logger.
This link contains important bpm 11g related blogs
- 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.
In order to easily identify the trace file you can set the trace file identifier as follows in ur AM..
getDBTransaction().executeCommand("ALTER SESSION SET tracefile_identifier = mysqltrace");
In the cases where you want to use your own Customization Class, make sure that this java class is available to jdeveloper when it restarts. Otherwise , when you use the "Customization Developer" role, you will see that in the Jdeveloper you will see messages like
MDS-00035: cannot load the class:xxxxx
and the customization context will be "none".
To prevent this one way is to create a jar file containing your Customization class and place it in
All the jar files placed in this directory are avaliable in the CLASSPATH when jdev restarts.
One windows if you get this error then just follow the steps below to set the virtual memory space and restart the machine and try to re install SOA suite.
1) Right click My Compter.
2) Select "Properties" from the context menu.
3) Select Advanced Settings
4) In the dialog that shows up select the "Settings" button in the "Performance" section
5) In the new dialog select "Advanced"
6) In the "Virtual Memory" section click the "Change" button.
7) Now deselect "Automatically manage paging file size for all drivers"
8) Now select "Custom size" and provide "Initial size" of 2 GB and Maximum size of "4 GB".
9) Click "Ok" in all the windows ..
Now restart the machine and try re-installing the soa suite.