Steps to configure a server agent in OWSM

-
Steps :-

To configure a server agent component in Oracle Web Services Manager
Point your browser to the Web Services Manager Control Console and log in using
your user name and password.
The Web Services Manager Control Console is accessed with a URL of the form:
http://:port_number/ccore
For example:
httphttp://samplexxxx:8888/ccore/index.jsp
2. Click Add New Component.
3. On the Add New Component page, define:
■Component name
■Component type
■Container type

Click Register.

Define Policy Set for Server Agent :-

To define the policy set for the server agent:
1. At the Web Services Manager Control Console, click Policy Management, then click Manage Policies.
2. In the component list, select the agent for which the policy set is to be defined, and click Policies.
3. The policy set for the agent is displayed.
4. Click the Edit icon for the Default Policy.
5. Select Extract Credentials from the list, and click OK.
6. The Policy Definition page reappears, showing the newly added Extract Credentials step.

Click Configure to define the properties for the Extract Credentials
steps :-
a. The Enabled property is set to true by default.
b. The credentials location is set to WS-BASIC.
8. Click OK.
9. To add the second step for credential authentication, in the Extract Credentials row, click Add Step Below.
10. In the New Step box, select the step template named LDAP Authenticate ; Configure LDAP connection

Install Server Agent on OC4J


1. At a Oracle Web Services Manager command prompt, navigate to the bin directory of the Oracle Web Services Manager component within Oracle SOA installation. For example:
ORACLE_HOME\owsm\bin
2. Using a text editor, edit the agent.properties file.
3. For the agent.component.id, insert the Component ID of the server agent that was registered
4. At the command prompt, run the installAgent command:
ORACLE_HOME\owsm\bin\wsmadmin installAgent Oracle-AS-password
where Oracle-AS-password is the OC4J administrator password.

Configure the Web Services Agent in Application Server Control

It is important to enable the Oracle Web Services Manager agent, Oracle Web Services
Manager and associate it with the Oracle WSM Server Agent.

To Configure the web services Agent in Enterprise Manager:

1. Open Application Server Control Console home page.
2. Under Members, click the home link.
3. Click Web Services. The list of web services is displayed.
4. Click the webservice link
5. Click the Administration link to display the management features available for
 this web service.
7. Select Web Service Agent and click Move. Press OK
8. Test the web service using registered username/password. Monitor the connections on OWSM.

Comments

Post a Comment

Popular posts from this blog

jstatd error : Could not create remote object : access denied (java.util.PropertyPermission java.rmi.server.ignoreSubClasses write)

-
While running "./jstatd -J-Djava.security.policy=jstatd.all.policy &" command , below error is getting encountered Error :- Could not create remote object access denied (java.util.PropertyPermission java.rmi.server.ignoreSubClasses write) java.security.AccessControlException: access denied (java.util.PropertyPermission java.rmi.server.ignoreSubClasses write) at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264) at java.security.AccessController.checkPermission(AccessController.java:427) at java.lang.SecurityManager.checkPermission(SecurityManager.java:536) at java.lang.System.setProperty(System.java:699) at sun.tools.jstatd.Jstatd.main(Jstatd.java:122) Cause :- The "access denied" error is expected, because "jstatd" requires a security policy file specified with the "java.security.policy" system property, if there is no security manager running on the machine. Solution :- 1) cd $ORACLE_HOME/jdk
Read more

Weblogic server is not starting up ; java.lang.AssertionError

-
  If the weblogic server is not starting up and giving the below error , please follow the below solution :- Error :- #Aug 18, 2014 12:34:29 AM PDT# #Notice# #WebLogicServer# #BEA-000365# #Server state changed to STARTING# #Aug 18, 2014 12:34:29 AM PDT# #Info# #WorkManager# #BEA-002900# #Initializing self-tuning thread pool# #Aug 18, 2014 12:34:29 AM PDT# #Notice# #Log Management# #BEA-170019# #The server log file /u01/app/oracle/config/domains/Vinay/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.# #Aug 18, 2014 12:34:29 AM PDT# #Critical# #WebLogicServer# #BEA-000386# #Server subsystem failed. Reason: java.lang.AssertionError: Could not obtain the localhost address. The most likely cause is an error in the network configuration of this machine. java.lang.AssertionError: Could not obtain the localhost address. The most likely cause is an error in the network configuration of this machine.                 a
Read more

ORA-22990: LOB locators cannot span transactions

-
Below is the error reported in BPEL opmn logs :- ############ <2010-02-07 10:50:59,852> <:logerror>Error while invoking bean "cube engine": Cannot update lob column.The process domain was unable to update the lob column "3" in the datastore. The exception reported is: ORA-22990: LOB locators cannot span transactions Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid. sql statement: BEGIN INSERT INTO cube_scope( cikey, domain_ref, scope_bin ) VALUES ( ?, ?, '0' ) RETURNING scope_bin INTO ?; END; ORABPEL-04040 Cannot update lob column. The process domain was unable to update the lob column "3" in the datastore. The exception reported is: ORA-22990: LOB locators cannot span transactions Please check that the machine hosting the datasource is physically connected to the network. Oth
Read more