Difference between SID and Service for WLST Config

How to define a datasource in Oracle WebLogic WLST Configuration

For a SID:
<attribute name="Url" value="jdbc:oracle:thin:@hostname:1521:SID" />

For a Service:
<attribute name="Url" value="jdbc:oracle:thin:@hostname:1521/Service" />

javax.security.auth.callback.UnsupportedCallbackException: [Security:090175]

Application throwing Unrecognized Callback exception when connecting through t3:
javax.security.auth.callback.UnsupportedCallbackException: [Security:090175]Unrecognized Callback com.abc.def.security.identityassertion.DramaCallback@32a4755]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:44)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:788)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:675)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:469)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:376)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.Environment.createInitialContext(Environment.java:208)
at weblogic.jndi.Environment.getInitialContext(Environment.java:192)
at weblogic.jndi.Environment.getInitialContext(Environment.java:170)
at weblogic.jndi.Environment.getContext(Environment.java:215)

Normally the application works fine when connected through http protocol.
Following are the suggestions to get rid of this error:
1. Move the default SQL authenticator to the top and make it sufficient
2. Don't throw any exception when UnsupportedCallbackException is caught during callback handler handle call

However you may need to watch out for the pros and cons of these solutions provided here.

Default Roles not listed when using RolePolicyManager api

When using RolePolicyManager api, default roles are not listed
If no roles are created by default following two roles are provided for each portal web application:
- AnonymousVisitor
- AuthenticatedVisitor
These can be verified using portal admin console, however these never appear when using the following api:
RolePolicyManager.listRolesForResource(EARName, WEBName, EntitlementConstants.P13N_ROLE_POLICY_POOL);
To make these default roles visible, create a custom role in the web application and same api will list all the three roles:
- AnonymousVisitor
- AuthenticatedVisitor
- Custom role

Find out if database sessions are locked

To Check if there is any database session locked

SELECT s1.username || '@' || s1.machine
    || ' ( SID=' || s1.sid || ' )  is blocking '
    || s2.username || '@' || s2.machine || ' ( SID=' || s2.sid || ' ) ' AS blocking_status
    FROM v$lock l1, v$session s1, v$lock l2, v$session s2
    WHERE s1.sid=l1.sid AND s2.sid=l2.sid
    AND l1.BLOCK=1 AND l2.request > 0
    AND l1.id1 = l2.id1
    AND l2.id2 = l2.id2 ;

select * from v$lock
select * from v$session

Display the session count, max sessions, highwater etc.
select sessions_max, sessions_current, sessions_highwater from v$license;

Oracle sample queries

Sample Oracle queries run on 11g (and 10g comparisons)

Query to display stored procedures:
select OBJECT_NAME from user_procedures
select OBJECT_NAME from user_objects where object_type = 'PROCEDURE'
both returns list of stored procedures
"select OBJECT_NAME from user_procedures" returns the stored procedures and triggers as well for Oracle 11g while
"select OBJECT_NAME from user_objects where object_type = 'PROCEDURE'" returns list of stored procedures only

select * from user_sequences
select * from user_objects where object_type = 'SEQUENCE'

select * from user_tables
select * from user_objects where object_type = 'TABLE'

select * from user_triggers
select * from user_objects where object_type = 'TRIGGER'

select * from user_indexes in 10g returns the LOB as well
select * from user_objects where object_type = 'INDEX'

Display all the roles, previleges, tables
select * from user_tab_privs order by grantee, table_name

Display all the synonyms for the table owner
SELECT * FROM all_synonyms where table_owner = 'XYZ' order by owner, synonym_name;

Select from a table and concat two or more columns
SELECT column1_name || ' # ' || column2_name  as column_both FROM table_name

Grant Privileges on tables/sequences to a role
grant select/insert/update/delete on [Schema].[Table/Sequence] to [Role_Name];

Create public synonyms for table, views, sequences

Create public synonyms for table, views, sequences for the schema XYZSchema


declare
  CURSOR xcur is
    select object_name, object_type from all_objects
where object_type IN ('TABLE', 'VIEW', 'SEQUENCE')
and owner = 'XYZSchema'
     ;

    xdat xcur%ROWTYPE;

begin
  for xdat in xcur loop
    begin
      execute immediate 'create or replace public synonym '|| xdat.object_name || ' for XYZSchema.'||xdat.object_name;
    exception when others
     then null;
    end;
   end loop;
 end;
/

Creating 10.3.4 WebLogic Portal domain with different port - simpler way

Follow the steps below while running Domain Configuration Wizard:
Step 1:
Open domain configuration wizard and select "WebLogic Portal - 10.3.4.0", click Next
Enter the domain name and choose domain location, click Next
Enter user name, password etc., click Next
Select the JDK, click Next

Step 2:
By now you should be in "Configure JDBC Data Sources" section of the wizard.
Select all the datasources and change the "Port" number as you wish i.e. 1557, click Next
All the tests will fail, thats ok, click Next, click OK, click Next

Step 3:
By now you should be in "Select Optional Configuration" section of the wizard.
Select "Administration Server" and click Next.
Change the port number as you wish and click Next, click Create and click Done.

Step 4:
Open database.properties file and replace these two lines:
derby.driver=org.apache.derby.jdbc.EmbeddedDriver
derby.url=jdbc:derby:weblogic_eval;create=true
with
derby.driver=org.apache.derby.jdbc.ClientDriver
derby.url=jdbc:derby://localhost:1557/weblogic_eval;create=true
save and close the file.

Step 5:
Open config.xml and change the port number as changed, save and close the file.
Open p13nProfileDataSource-jdbc.xml and change the port number as changed, save and close the file.

Step 6:
Open startWebLogic.cmd and replace the word 
- stopNetworkServer.cmd with stopNetworkServer_vkb.cmd
- startNetworkServer.cmd with startNetworkServer_vkb.cmd
save and close the file.

Open stopWebLogic.cmd and replace the word 
- stopNetworkServer.cmd with stopNetworkServer_vkb.cmd
save and close the file.

Step 7:
Go to wlserver_10.3\common\derby\bin folder
Copy following files:
- startNetworkServer.bat
- startNetworkServer.cmd
- stopNetworkServer.bat
- stopNetworkServer.cmd
and paste and rename as followings:
- startNetworkServer_vkb.bat
- startNetworkServer_vkb.cmd
- stopNetworkServer_vkb.bat
- stopNetworkServer_vkb.cmd

Step 8:
Open startNetworkServer_vkb.bat and replace the port number to 1557,  save and close the file.
Open stopNetworkServer_vkb.bat and replace the port number to 1557,  save and close the file.
Open startNetworkServer_vkb.cmd and replace the word startNetworkServer.bat with startNetworkServer_vkb.bat,  save and close the file.
Open stopNetworkServer_vkb.cmd and replace the word stopNetworkServer_vkb.bat with stopNetworkServer_vkb.bat, save and close the file.

Step 9:

Go to domain folder and run the script crate_db.cmd,  it should create the portal database to the new port.

You are good to go now!

Default Transaction Attribute for EJBs

Default transaction attributes differ from container to container.
In Weblogic Server, default transaction attribute for MDB is NotSupported however for all other EJBs is Supports for version 10.0 onwards - if no attribute value is specified for trans-attribute in the ejb deployment descriptor.

Container-Managed Transaction Elements in ejb-jar.xml (WebLogic Server 10.x)

Element: transaction-type
Description: Allowable values are Bean or Container.
Default: None, EJB 2.x requires this attribute to be specified.

Element: trans-attribute

Description: 

Specifies how the container manages the transaction boundaries when delegating a method invocation to an enterprise bean's business method. Allowable values are:

• NotSupported
With the NotSupported value, when an entity bean runs in an unspecified transaction, if a transaction exists, the EJB container suspends the transaction; when an entity bean runs in an unspecified transaction, and no transaction exists, the EJB container takes no action.
• Supports
With the Supports value, when an entity bean runs in an unspecified transaction, if a transaction exists, the EJB container uses the current transaction; when an entity bean runs in an unspecified transaction, and no transaction exists, the EJB container takes no action.
• Required
• RequiresNew
• Mandatory
• Never
With the Never value, when an entity bean runs in an unspecified transaction, if a transaction exists, the EJB container throws an exception; when an entity bean runs in an unspecified transaction, and no transaction exists, the EJB container takes no action.

Note: In in pre-9.0 releases of WebLogic Server, the EJB container would start a new transaction when no transaction existed and the value of trans-attribute was NotSupported, Supports, and Never. Set entity-always-uses-transaction inweblogic-ejb-jar.xml to True if you want the EJB container to behave as it did in pre-9.0 releasesof WebLogic Server and create a new transaction.

Because clients do not provide a transaction context for calls to an MDB, MDBs that use container-managed transactions must have trans-attribute of Required.

Default: If not specified, the EJB container issues a warning, and usesNotSupported for MDBs and Supportsfor other types of EJBs.

Element: transaction-scope

Description: 

This optional element specifies whether an enterprise bean requires distributed transactions for its methods or whether the local transaction optimization may be used.

Allowable values are Local and Distributed.

Default: If not specified, the container assumes that distributed transactions must be used.

Reference: http://docs.oracle.com/cd/E11035_01/wls100/ejb/implementing.html#wp1150418

Return List of Dynamic object types from Method

Sometimes we want to convert the list of objects into a desired data type list. Here is one simple example which returns a list of objects into list of Strings, assuming that all the objects will be of type String.

// method with generic return type
public <T> List<T> getMyList(Class<T> elementType, List objList)
{
    List<T> list = new ArrayList<T>();
    
    for(Object obj : objList)
    list.add(elementType.cast(obj));
    
    return list;
}

// calling the method
getMyList(String.class, objList);