Changing Oracle Soa Suite Password for oc4jadmin user

Today , i got stuck at something. After a long time , i started my  local SOA suite and went to log in to the em , to find that i had forgotten the oc4jadmin password.After going through many forums , found this useful information.

To reset the password ,

1. Stop the application server

2. Open the file <ORACLE_HOME>\j2ee\home\config\system-jazn-data.xml

3. Locate the following lines
   
             <user>
                <name>oc4jadmin</name>
                <display-name>OC4J Administrator</display-name>
                <guid>0BF5F200BED611DEBFF009542E70BEF5</guid>
                <description>OC4J Administrator</description>
                <credentials>{903}az65wT6YFcIuCWFAF8MewMy7qHLkUzFMk+bZ1WPztOk=</credentials>
            </user>

4. Replace the credentials node with with  : !newpassword123 (Follow the default password rules.Also there must be a '!' in front  of the new password)

5. Start the application server

6. Log in to EM

7. It will throw RMI error and will ask to store the new password

8. Input the new password  and you will be taken to the landing page

Domain level Logging configuration in Oracle BPEL Console

This  blog is regarding how to set audit levels in the BPELConsole , so that you can toggle between system performance and information required as a part of performance tuning the BPEL processes


These are four logging levels available through BPELConsole

• off
• minimal
• production
• development

Go the particular domain you want to configure and then click on the 'Configuration' tab
In the Domain sub tab , there is a editable property (Depend on the access level set to your user , it might be editable or non editable) auditLevel.

This is the description that oracle has  given alongside the property

Controls the amount of audit events logged by a process; currently supported logging levels are:
off - absolutely no logging performed whatsoever; may result in a slight performance boost for processing instances.
minimal - all events are logged; however, no audit details are logged.
production - all events are logged. The audit details for assign activities are not logged; the details for all other nodes are logged.
development - all events are logged; all audit details for all actitivies are logged.
The default value is "development".


When we set the property to 'development' , we can see all the the logging that is possible - both instance level and payload level.
This is ideal for a development environment where the debugging required is high.The activities contain payload data , like the one below

Using this in production is not advisable , but yet i have used this for momentary tracking / debugging.

Using 'production' is the optimal level for a production environment . When you use this , the audit trail doesn't show any payload.The assign activities (assign , transform etc) don't show any details like the down below.

When i set this to Minimal,ZERO audit details are logged but All the events are logged.Look the below screen shot.None of the audit in any activity can b seen , but we can see all the events !!






Off : nothing is logged.. Use this if your server has minimum configuration but the transaction you need to handle is more !!
      Not advisable as it will be like roaming in a sea without a compass.But yet , if you have a robust development cycle  then this can be used , just like a well known sailor who knows the depth and directions in a sea

Generating artifacts for invoking a stored procedure in MSSQL server and IBM DB2

1. Set the operating system classpath to contain the following java library  files found in jdeveloper installation
1. ocrs12.jar
2. ojdbc14.jar
3. ojdbc14dms.jar
4. orai18n.jar
5. sqljdbc.jar
6. DBAdapter.jar
7. bpm-infra.jar
8. orabpel.jar
9. xmlparserv2.jar
10. xschema.jar
11. toplink.jar

    eg : set classpath=%classpath%;d:\jdevstudio10134\jdbc\lib\ocrs12.jar; d:\jdevstudio10134\jdbc\lib\ojdbc14.jar; d:\jdevstudio10134\jdbc\lib\ojdbc14dms.jar; d:\jdevstudio10134\jdbc\lib\orai18n.jar; d:\jdevstudio10134\jdbc\lib\sqljdbc.jar;

Note: If any of the jar is missing in the jdeveloper/SOA suite installation, the jar can be downloaded from http://www.findjar.com/

2. Prepare the properties file that will be consumed by the java tool

The properties file should have

ProductName=<Database product>

DriverClassName=<Driver to be used>

ConnectionString=<JDBC Connection String>

Username=<username here>

Password=<password here>

DatabaseName=<MSSQL database>

SchemaName=dbo

ProcedureName=<name of the procedure here>

ServiceName=<Service name. This will be the name of the wsdl generated and referenced>

DatabaseConnection=<OC4Jra.xml connection string that the artificat will use>

Eg : dbname.Properties

ProductName=Microsoft SQL Server

DriverClassName=com.microsoft.sqlserver.jdbc.SQLServerDriver

ConnectionString=jdbc:sqlserver://xx.xx.xx.xx:xxxx;databaseName=dbname

Username=dbusername

Password=XXXXX

DatabaseName=dbname

SchemaName=dbo

ProcedureName=spiCSIncidentTaskFromSOA

ServiceName=srv_CSTask

DatabaseConnection=eis/DB/dbname

3. Use the below command to generate artifacts using the above properties file

C:\Jdev10.1.3.4\integration\lib>java oracle.tip.adapter.db.sp.artifacts.GenerateArtifacts dbname.Properties

3. The tool will generate two WSDL file and  an XSD
4. Import the Project WSDL into the BPEL Project
5. Create a partner link for the imported wsdl
6. Create a Invoke activity and map it to the new partner link