2 way SSL

Implement the weblogic proxy plugin for the Apache web server.

Copy the mod_wl_20.so  to <APACHE_HOME>\modules. 

Modify the httpd.conf file located in <APACHE_HOME>\conf

LoadMoadule:

to load mod_wl_20.so and add the module specific configuration.


Cluster Configuration:

<IfModule mod_weblogic.c>

    WebLogicCluster 127.0.0.1:7003,127.0.0.1:7005,127.0.0.1:7007

    MatchExpression /*

</IfModule>

<Location /weblogic>

    SetHandler weblogic-handler

    WebLogicCluster 127.0.0.1:7003,127.0.0.1:7005,127.0.0.1:7007

    DebugConfigInfo ON

    PathTrim /weblogic

</Location>

No more weblogic.Admin utility in 12.2.1

weblogic.Admin

The weblogic.Admin utility has been removed from Oracle WebLogic Server 12.2.1.

Apache http server Installation

Apache is one of the most popular web servers, and part of its charm is that it's free. It also has a lot of features that make it very extensible and useful for many different types of websites. It is a server that is used for everything from personal web pages to enterprise level sites.

This article will discuss how to install Apache on a Linux system.


Download Apache

ex: httpd-2.0.55.tar

setp1:

gunzip -d httpd-2_0_NN.tar.gz
tar xvf httpd-2_0_NN.tar

This creates a new directory under the current directory with the source files.
Configuring Your Server for Apache

Once you've got the files, you need to tell your machine where to find everything by configuring the source files. The easiest way is to accept all the defaults and just type:

setp2:

./configure --prefix=/home/soa/apache/apache2

   
To configure the source tree using all the default options, simply type ./configure. To change the default options, configure accepts a variety of variables and command line options.

The most important option is the location --prefix where Apache is to be installed later, because Apache has to be configured for this location to work correctly. More fine-tuned control of the location of files is possible with additional configure options.

As with any source installation, you'll then need to build the installation:

setp3:

make

make install

Customize Apache configuration

Assuming that there were no problems, you are ready to customize your Apache configuration. This really just amounts to editing the httpd.conf file. This file is located in the PREFIX/conf directory. I generally edit it with text editor.

vi PREFIX/conf/httpd.conf

setp4:

vi /home/soa/apache/apache2/bin/httpd.conf

by default we have 80 port.If we have custom port number we can change like below.

step5:

Navigate to apache_home/bin>

apache_home=/home/soa/apache/apache2

[soa@soa12c-12-1-3 bin]$ ./apachectl start



Open a web browser on the same machine and type http://192.168.0.21:8080/ in the address box. You should see a page similar to the one in the partial screen shot below. 

Oracle 12c "Composite Lazy Loading"

In SOA 12c, Oracle has introduced a new feature known as 'Composite Lazy loading'. This is one of the nice features, in which any server initialization tasks such as loading components and resources like WSDLs and XSDs, are loaded later at first-request time when they are needed, which means that server will only create in-memory java models and MBeans. It improves server startup time when there is a large number of composites deployed on it.

Details:
Composite Lazy Loading can be configured at two levels

1) Domain 

2) Component Level

Lazy Loading at Domain Level:
This setting can be disabled/enabled from System MBean Browser in FMW EM console. Follow below steps:
1. Login to EM Console, right-click on the domain you want to tune and select System MBean Browser from the drop-down menu

2. In the System MBean Browser folder structure, navigate through: Application Defined MBeans --  oracle.as.soainfra.config -- Server: ServerName -- SoaInfraConfig -- soa-infra

3. When you click on soa-infra, its attributes will be listed in on the right. Look for the CompositeLazyLoading attribute and click on it. You can set the value to true to enable it or
false to disable it

4. Click Apply and restart the server for changes to take effect.

 

Difference between wls.jar and fmw_infra.jar in Weblogic

wls_121200.jar

Installs WebLogic Server and Coherence

fmw_infra_121200.jar

Installs WebLogic Server, Coherence, and infrastructure components for Fusion Middleware product platforms.

Thumb Rule in java Tuning

The best way to tune in Java, needs to follow the Thumb Rule.

Thumb Rule: Try to maximize objects reclaimed in young men and Minimize Full GC frequency.

Difference between messaging bridge and foreign JMS server

Both of the messaging bridge and the foreign JMS server allow you to receive/send messages via a WLS server to a JMS destination that is running on a remote WLS server/cluster/domain or a 3rd party messaging product.

The differences are:
1. Messaging bridge is sort of a store-and-forward solution; messages are stored in the source destination and are forwarded to the target destination, while foreign JMS server directly accesses the remote destination.

2. Messaging bridge introduces one extra hop; messages are sent to and stored in a destination (source destination) and forwarded to another destination (target destination), while foreign JMS server directly accesses the remote destination;

3. Usually one messaging bridge is used in single direction; applications send messages to the source destination and receive messages from the target destination, while foreign jms server is bi-directional; application can send and receive from the same foreign JMS destination.

If you don't need store-and-forward capability, Foreign JMS server is more desirable and easy to configure. You may consider use the messaging bridge if you need to handle disconnected case, say you want to be able to send messages when the remote destination is down. If both local and remote servers are WLS 9.0 and later, you could also consider using store-and-forward feature, instead of the messaging bridge.

Adding Gropus to GlobalRoles using WLST

WLST script 

connect('weblogic','weblogic1','t3://192.168.195.129:8001') 
serverConfig()
cd('/SecurityConfiguration/pocdomain/Realms/myrealm/RoleMappers/XACMLRoleMapper')
cmo.setRoleExpression(",'Admin','Grp(EnvAdmins)|Grp(Administrators)')

How to find 12c RCU profile(Large/Medium/Small)

If you want to find RCU category /profile in 12c please run the below command in SOAINFRA schema

select * from version

Error [Management:141191]The prepare phase of the configuration update failed with an exception

An error occurred during activation of changes, please see the log for details.
Message icon – Error [Management:141191]The prepare phase of the configuration update failed with an exception:
Solutions-
-> First thing never try to delete any managed server which is up and running.First shut down and then closed it.

Follow below steps to get rid of this error

-> Stop the Admin Server & Managed Servers which is up and running.
-> On your Admin Server cd to $WLS_HOME\user_projects\domains\base_domain.
-> Delete all files in pending and servers/domain_bak directory.
-> Start the Admin Server & Managed Servers.
-> Login the weblogic Admin Console and click on Release Configuration button.
-> Perform the same changes now.

How to Change the OPSS Schema Password

1- Stop all WLS servers

2- Change the DATA source password with WLST (offline)

2.1- Run  $MW_HOME/oracle_common/common/bin/wlst.sh to set the wlst environment.

2.2- Use the readDomain WLST command to read the configuration of the domain in offline mode,
wls:/offline>readDomain (‘<WLS_DOMAIN_HOME_PATH>’)
Example:

wls:/offline> readDomain('/opt/Middleware/user_projects/domains/soa_domain')
2.3- Use cd(‘JDBCSystemResource/<OPSSDS name>/JdbcResource/<OPSSDS name>/JDBCDriverParams/NO_NAME_0’) 
Where "OPSSDS name" is data source name. The data source name can be found in DOMAIN_HOME/config/jdbc/opss-jdbc.xml.
Example:

wls:/offline>cd('JDBCSystemResource/OPSSDS/JdbcResource/OPSSDS/JDBCDriverParams/NO_NAME_0')
2.4- The WLST set(‘<parameter_name>’,’<parameter_value>’) is used to change a parameter offline. To change the password ,  set(‘PasswordEncrypted’,’<password_value>’)
Example:

wls:/offline/soa_domain/JDBCSystemResource/OPSSDS/JdbcResource/OPSSDS/JDBCDriverParams/NO_NAME_0>set('PasswordEncrypted','welcome2')
2.5- After all the changes to the parameters are done, the updateDomain() command needs to run to save them to the domain configuration:
Example:

wls:/offline/soa_domain/JDBCSystemResource/OPSSDS/JdbcResource/OPSSDS/JDBCDriverParams/NO_NAME_0>updateDomain()
2.6- Run  exit() to exit WLST. 
Example:

wls:/offline/soa_domain/JDBCSystemResource/OPSSDS/JdbcResource/OPSSDS/JDBCDriverParams/NO_NAME_0>exit()
2.7- Run exit() to exit WLST.
Example:

wls:/offline/soa_domain/JDBCSystemResource/OPSSDS/JdbcResource/OPSSDS/JDBCDriverParams/NO_NAME_0>exit()
Later:

3- Change the OPSS schema password in the database

4- The next steps are required if there is a bootstrap credential map specified in the "props.db.1" section in jps-config.xml
Go to the oracle_common\common\bin>wlst.sh

5- Run modifyBootStrapCredential(jpsConfigFile='./jps-config.xml', username='<schema_owner>', password='<db user password>')
Example:

modifyBootStrapCredential(jpsConfigFile='/opt/Middleware/user_projects/domains/soa_domain/config/fmwconfig/jps-config.xml', username='DEV_OPSS', password='welcome1')

Enable coherence for SOA Servers

Please follow the below steps to enable coherence for SOA Servers.

ms01- 

hostname=soaserver1.us.com
portnumber=50561

ms02- 

hostname=soaserver2.us.com
portnumber=50562

Please add the fololwoiing enttires into server start arugemtns 

ms01--> configuration --> ServerStart --> Arguments 


ms01 

-Dtangosol.coherence.wka1=soaserver1.us.com -Dtangosol.coherence.wka2=soaserver2.us.com -Dtangosol.coherence.localhost=soaserver1.us.com -Dtangosol.coherence.wka1.port=50561 -Dtangosol.coherence.wka2.port=50562 -Dtangosol.coherence.localport=50561 -Dtangosol.coherence.log=/opt/domains/soa_domain/coherence_ms01.log -Dtangosol.coherence.log.level=9 

ms02--> configuration --> ServerStart --> Arguments 

ms02 

-Dtangosol.coherence.wka1=soaserver1.us.com -Dtangosol.coherence.wka2=soaserver2.us.com -Dtangosol.coherence.localhost=soaserver2.us.com -Dtangosol.coherence.wka1.port=50561 -Dtangosol.coherence.wka2.port=50562 -Dtangosol.coherence.localport=50561 -Dtangosol.coherence.log=/opt/domains/soa_domain/coherence_ms02.log -Dtangosol.coherence.log.level=9 

Reset the AdminServer Password in WebLogic 11g and 12c

If you forget the AdminServer password for your WebLogic 11g domain, you can reset it from the command line using the following process.

Set up the following environment variables. They are not necessary for the process itself, but will help you navigate. In this case my domain is called "ClassicDomain". Remember to change the value to match your domain.

export MW_HOME=/u01/app/oracle/middleware
export DOMAIN_HOME=$MW_HOME/user_projects/domains/ClassicDomain
Shut down the WebLogic domain.

$ $DOMAIN_HOME/bin/stopWebLogic.sh
Rename the data folder.

$ mv $DOMAIN_HOME/servers/AdminServer/data $DOMAIN_HOME/servers/AdminServer/data-old
Set the environment variables.

$ . $DOMAIN_HOME/bin/setDomainEnv.sh
Reset the password using the following command. Remember to substitute the appropriate username and password.

$ cd $DOMAIN_HOME/security
$ java weblogic.security.utils.AdminAccount <username> <password> .
Update the "$DOMAIN_HOME/servers/AdminServer/security/boot.properties" file with the new username and password. The file format is shown below.

username=<username>
password=<password>
Start the WebLogic domain.

$ $DOMAIN_HOME/bin/startWebLogic.sh