How to checks the logs for Weblogic/SOA/OIM and OAM Servers in Linux

Server Log locations :

1. Weblogic Server : $DOMAIN_HOME/servers/Admin_server and view admin_server_diagnostic.log

2. SOA Server : $DOMAIN_HOME/servers/soa_server1 and view soa_server1_diagnostic.log

3. OIM Server : $DOMAIN_HOME/servers/oim_server1 and view oim_server1_diagnostic.log

4. OAM Server : $DOMAIN_HOME/servers/oam_server1 and view oam_server1_diagnostic.log

Configure SSL for Managed Server

Configure SSL for Managed Server

This process should be followed for the AdminServer and all managed servers.

• In the WebLogic Server Administration Console, click on <Servers> in the <Domain Structure> tree.
• Click on the <managed server> you wish to configure.
• Click on the <Configuration >- <Keystores> tab and sub-tab.
• If you are running on production mode, click the <Lock & Edit> Button.
• Click the <Change> button next to the <Keystores> setting.
• Select the <Custom Identity and Custom Trust> option and click the <Save> button.

• Enter the identity details. For example.
• Custom Identity Keystore: /home/oracle/keystore/identity.jks
• Custom Identity Keystore Type: JKS
• Custom Identity Keystore Passphrase: password1
• Confirm Custom Identity Keystore Passphrase: password1

• Enter the trust information. For example.
• Custom Identity Keystore: /home/oracle/keystore/trust.jks
• Custom Identity Keystore Type: JKS
• Custom Identity Keystore Passphrase: password1
• Confirm Custom Identity Keystore Passphrase: password1

• Click the <Save> button.
• Click the <SSL> tab.

• Enter the identity details. For example.
• Private Key Alias: selfsigned
• Private Key Passphrase: password1
• Confirm Private Key Passphrase: password1

• Click the <Save> button.
• If you are running in production mode, click the <Activate Changes> button.
• Restart the managed server.

The managed server will now be using the new identity and trust keystores.

Boot Identity File for SOA

How to create Boot Identity File for SOA

Version: SOA 11.1.1.5.0, SOA 11.1.1.6.0

Weblogic Contains out of box scripts to start up your Weblogic server instances like startWebLogic.cmd and startManagedWeblogic.cmd on Windows. Whenever you run these scripts, you are prompted to enter weblogic administrator credentials.

What is boot identity file:

It is a file which contains user credentials for starting and stopping an instance of Weblogic Server.

Steps:

1. Create a boot.properties file under 

$MW_HOME\user_projects\domains\domain_name\servers\soaserver1\security

On windows: create boot.properties manually 
On Linux: touch boot.properties

2. In the boot.properties file, provide weblogic username and password and save the file

Example: username=weblogic
              password=enter password here

3. Start Admin Server and then start SOA Managed Server.The boot.properties file will get encrypted and you will no longer be prompted for a username and password when starting the weblogic administration server and SOA Managed Server