Showing posts with label Configuration. Show all posts
Showing posts with label Configuration. Show all posts

How to change the timeout of EM console in SOA 11g ?

1. In your SOA installation look for "emoms.properties" file
The path should be somewhere in your SOA_HOME under domains folder

SOA_HOME/user_projects/domains/base_domain/servers/AdminServer/tmp/_WL_user/em/hsz5x1/META-INF/emoms.properties

2. Edit the file and add the line


oracle.sysman.eml.maxInactiveTime= < value >

where Value it's in minutes

4. Restart Admin & SOA server.

Posted in Labels: , , , | 0 comments

How to change the timeout of EM console in SOA 11g ?

1. In your SOA installation look for "emoms.properties" file
In my env the path is
/home/oracle/product/11g/user_projects/domains/base_domain/servers/AdminServer/tmp/_WL_user/em/hsz5x1/META-INF/emoms.properties

2. Make a backup copy of it

3. Edit the file and add the line
oracle.sysman.eml.maxInactiveTime=< value >
where VALUE it's in MINUTES

4. Restart Admin & SOA server.

Posted in Labels: , , , | 0 comments

How to Reset CAMM Admin Account Password

If you forgot the password for "admin" account , this is a simple way to reset it  .

Look in your CAMM install folder for file "AccessControl.xml"


You should see following section regarding the "admin" account:


<user userid="admin" enabled="true">
<first>Default</first>
<last>Administrator</last>
<password> --- encoded password --- </password>

If you want to reset the password you can set it to

<password>0DPiKuNIrrVmD8IUCuw1hQxNqZc=</password>

and next login as user "admin" with password "admin" .

Posted in Labels: , | 0 comments

Active Directory and SOA 11g

. Login to Weblogic Console ( http://host:7001/console) and go to
Security Realms -> myrealm -> Providers

2. Click on "New" to create a new Provider. Let's assume you will call this provider AD.
You must select ActiveDirectoryAuthenticator as provider type.
Click OK.


3. Now , you should have the following list of providers. At this point we need to reorder the provider
list so that AD will be the first one. This step is needed for Worklist application, otherwise you
will not be able to login with the AD users in worklist.


After reordering you should have the following list of providers


4. Click on AD provider and then open the tab Provider Specific .
NOTE : this is an example, you should set the parameters to match your AD configuration.

The rest you can leave unchanged for now. Click Save.



5. Now edit BOTH the AD and the DefaultAuthenticator provider and set
Control Flag: SUFFICIENT




6. Restart Admin and SOA managed server to activate the changes

7. Create a new User in AD - let's call it 'dummy'

8. Look in Weblogic Console at "Users and Groups" in "myrealm" . You should be able to see the new AD user "dummy"

9. Now try to login to worklist (http://host:8001/integration/worklistapp/)
You should be able to login with "dummy" user .

Posted in Labels: , , , | 2 comments

ServerURL and Callback Server URL in SOA 11g

When you want to test a composite in SOA 11g you will see something similar to this screenshot :




You would want to change the "localhost.localdomain" part of the URL to some other hostname - for example I will use "deskLinux". To do this you need to modify the ServerURL and CallbackServerURL in the SOA configuration. This can be easily done via SOA Enterprise Manager :

1. Right Click on SOA-INFRA component in the left navigation tree. Go to Soa Administration --> Common Properties



2. Set the CallBackServerURL and the ServerURL to  http://deskLinux:8001 and click Save button


3. Restart SOA server to activate the changes . The URL should now be modified for all composites.

Posted in Labels: , , | 0 comments

How to Set a Timeout for a Web Service in SOA 11g ?

In 11g SOA we don't have anymore the "Timeout" property that we can put in Web Service invocations to set a maximum wait time in a sync BPEL invocation - so the solution presented in Setting a Timeout for a WebService invocation in BPEL will not work anymore in BPEL 11g.

I will explain below how to set a TIMEOUT on a Web Service invocation when using SOA 11g . This can only be used when only Web Service invocation is made through HTTP.

1. For a process that invokes a Web Service, we want to set a timeout of maximum 10 seconds that the SOA application will wait for the answer. If no response is received within the specified timeout, then we want to catch the timeout error and perform a series of other activities.

The sample below is for a BPEL in a SOA Composite - it will work the same way with Mediator as the timeout is set in composite.xml file and not in some specific BPEL file .

2.  Let's say the SOA composite looks like this:

 
3. Click on  "Service1" and note that the property inspector will open in the lower right side of your JDeveloper window. Here set the property :


oracle.webservices.httpReadTimeout = 10000   (in MiliSeconds)

If the Web Service is on the same domain as the SOA Composite , you will also have to set :

oracle.webservices.local.optimization = false  

By default the local optimization is TRUE and when a SOA composite invokes another SOA composite within the same Weblogic (WLS) server or cluster of WLS servers bypasses the whole SOAP stack, and makes a direct java call to optimize the invocation .







 You may set these properties directly in composite.xml 

<reference name="Service1"
ui:wsdlLocation="http://localhost:8001/soa-infra/services/default/Child!1.0/Child.wsdl">
<interface.wsdl interface="http://xmlns.oracle.com/test/Child/Child#wsdl.interface(Child)"/>
<binding.ws port="http://xmlns.oracle.com/test/Child/Child#wsdl.endpoint(child_client_ep/Child_pt)"
location="http://localhost:8001/soa-infra/services/default/Child!1.0/child_client_ep?WSDL">
<property name="oracle.webservices.local.optimization">false</property>
<property name="oracle.webservices.httpReadTimeout" type="xs:string" many="false">10000</property>
</binding.ws>
</reference> 
 
4. This timeout will throw a RemoteFault - so you can easily add a Catch to your BPEL code to catch this error.

5. Now deploy the composite and run it from EM page . The Web Service we are calling takes 40 seconds to complete , but we set the timeout to 10 seconds - note that the Remote Fault occurs after 10 seconds.


 

Posted in Labels: , , | 4 comments