How To - OWSM 10.1.3 : Add help page for custom steps

You can add a help page for custom policy step in 10.1.3.1 Oracle Web Services Manager (OWSM) by following these steps:

1. Navigate to the OC4J_HOME/owsm/lib/app/ccore/help/steps directory


2. Create the html help page for the custom page here and name it with the step name replacing any spaces with underscore. For example, if the step name is “My Custom Step” then name the help page as My_Custom_Step.html

You can optionally create help pages in other languages and put them under the respective directories such as es, fr, etc.

1. Start the OC4J server


2. On command prompt, go to OC4J_HOME/owsm/bin directory and run the following command

wsmadmin deploy OC4J_ADMIN_PASSWORD control

This will package the control application again with the newly added help page, and redeploy it into the OC4J container.

Login to the OWSM Control. Help for your custom step should be available now.

FAQ - OWSM 10.1.3 : Types of logging

Oracle Web Services Manager (OWSM) 10.1.3.1 performs 2 types of logging.

1. Message logs - This can be configured in the policy as a policy step. The SOAP message is logged/stored in the database.

2. Diagnostic logs - These logs are written into filesystem at ORACLE_HOME/j2ee/OC4J_Instance/log.
Each of the OWSM application has their own logs - gateway.log, serveragent.log, clientagent.log, policymanager.log, monitor.log, ccore.log.
To get detailed diagnostic logging, the log level can be changed as per this post.

Additionally, customers can implement custom policy step to send message logs to a centralized logging application. Refer to OWSM Extensibility guide for creating custom policy steps.

How To - OWSM 10.1.3 : Change log level

The out-of-box log level is “INFO” for all OWSM applications. For debugging purposes, you may want to bump this log level to get further details on the problem. Following instructions will allow you to achieve this.

OWSM Gateway

1. Make sure that OC4J application server is running.
2. Open OC4J_HOME/owsm/config/gateway/logging.xml and replace all “INFO” with “ALL”.
3. Go to OC4J_HOME/owsm/bin directory, and run the following command
   wsmadmin deploy OC4J_ADMIN_PASSWORD gateway
4. The changed log level for the gateway application is in effect now. Look for the detailed logs in OC4J_HOME/j2ee/OC4J_Instance/log/gateway.log

OWSM Control

1. Make sure that OC4J application server is running.
2. Open OC4J_HOME/owsm/config/ccore/logging.xml and replace all “INFO” with “ALL”.
3. Go to OC4J_HOME/owsm/bin directory, and run the following command
   wsmadmin deploy OC4J_ADMIN_PASSWORD control
4. The changed log level for the gateway application is in effect now. Look for the detailed logs in OC4J_HOME/j2ee/OC4J_Instance/log/ccore.log

OWSM Policy Manager

1. Make sure that OC4J application server is running.
2. Open OC4J_HOME/owsm/config/policymanager/logging.xml and replace all “INFO” with “ALL”.
3. Go to OC4J_HOME/owsm/bin directory, and run the following command
   wsmadmin deploy OC4J_ADMIN_PASSWORD policymanager
4. The changed log level for the gateway application is in effect now. Look for the detailed logs in OC4J_HOME/j2ee/OC4J_Instance/log/policymanager.log

OWSM Monitor

1. Make sure that OC4J application server is running.
2. Open OC4J_HOME/owsm/config/coreman/logging.xml and replace all “INFO” with “ALL”.
3. Go to OC4J_HOME/owsm/bin directory, and run the following command
   wsmadmin deploy OC4J_ADMIN_PASSWORD monitor
4. The changed log level for the gateway application is in effect now. Look for the detailed logs in OC4J_HOME/j2ee/OC4J_Instance/log/coreman.log

OWSM Agents on OC4J

Server Agent or J2EE Client Agent

1. Make sure that OC4J application server is running.
2. Open OC4J_HOME/owsm/config/interceptors/componentId/config/clientagent or serveragent/logging.xml and replace all “INFO” with “ALL”.
3. Restart the application.
4. The changed log level for the serveragent application is in effect now. Look for the detailed logs in OC4J_HOME/j2ee/OC4J_Instance/log/serveragent.log for serveragent (and clientagent.log for client agents).

How To - OWSM 10.1.3 : Change default password of admin user accessing OWSM Control when JSSO is disabled

When JSSO is disabled, Oracle Web Services Manager (OWSM) Control authenticate users at login time with the users present in a database table. To change the default password for the user "admin", follow these steps:
- delete admin user
- add admin user back
- add admin user to the super user group "su1-grp"

1. Go to OC4J_HOME/owsm/bin directory and modify manageUserGroups.properties
user_id=admin
user_name=admin user
user_password=yourNewPassword
user_email=admin@xyz.com

group_id=su1-grp
group_desc=super user group

2. Delete the existing admin user by executing
wsmadmin manageUserGroups deleteUser

4. Add the admin user again by executing
wsmadmin.bat manageUserGroups addUser

5. Add admin user to super user group
wsmadmin.bat manageUserGroups addUserGroup

The admin user password is changed.

Presenting Technical Session TS-8131 on Web Services Security in JavaOne 2007

I'll be presenting this technical session on Web Services Security alongwith Marc Chanliau (Director, Product Management, Oracle) in JavaOne 2007. Here are the session details.

Session ID: TS-8131
Session Title: Java Technology and Web Services Security in Action
Track: Services and Integration
Room: Esplanade 304/306
Date: 11-MAY-07
Start Time: 13:30

Summary: In service-oriented architecture (SOA), security and especially identity propagation are among the challenges IT organizations face today. Java EE and Jav SE provide standards and best practices, such as Java Authentication and Authorization Service (JAAS) and Java Authorization Contract for Containers (JACC), to ensure security in the platform, and web services also provide WS-Security standards for achieving secure communication and identity propagation. In this session, you find out how you can achieve identity propagation between services and business processes by using Java technology. The session introduces you to the various security standards of the Java platform and web services and demonstrates them in action by using an end-to-end scenario involving Java SE, Java EE applications (JAX-WS), business processes (BPEL), and the Enterprise Service Bus (ESB). You will see how Java technology-based security can be used in conjunction with WS-Security standards to encrypt, sign messages, and propagate the identity of users between the various actors of a classical SOA-based application.