Datasource is found to be in suspended state in WebLogic 10.3

Issue : Datasource is found to be in suspended state in WebLogic 10.3

Sol: 

If you see that any DataSource is in Suspended Mode then please first check the Server Logs...you may find one of the reason as "N/W disconnect from the Database". In this case you may try:
  1. Look at the Server Logs...related to JDBC information.
  2. Try to use the "utils.dbping" utility provided by WebLogic to test the connectivity between target Server Box and the Database. 
  3. If you see that the above step is able to establish the Connectivity with the database successfully then try to use the "weblogic.Admin" utility to Restore (Resume) the DataSource.

    You can use “weblogic.Admin” utility to Enable and Disable the Pool (DataSource) just to confirm whether the dataSource is actually active or not

1.Run the configuration script "setWLSEnv.sh" first.


To suspend:
java weblogic.Admin -url t3://localhost:<port> -username weblogic -password <password> SUSPEND_POOL YourDataSourceName             

To re-enable:
java weblogic.Admin -url t3://localhost:<port> -username weblogic -password <password> RESUME_POOL YourDataSourceName

If you get any exception or error while doing this it means there may be some database connectivity issue...

DBPing Utiity In WeblogicServer

DBPing :

The dbping command-line utility tests the connection between a DBMS and your client machine via a JDBC driver.

Syntax :

$ java utils.dbping ORACLE_THIN <USERNAME> <PASSWORD> <IP:PORT:SID>


Example

Source the environment using setDomainEnv.sh

[oracle@oracle basedomain]$ java utils.dbping ORACLE_THIN mani oracle 172.24.146.88:1581/mani

OUTPUT :

**** Success!!! ****
You can connect to the database in your app using:
java.util.Properties props = new java.util.Properties();
props.put("user", "mani");
props.put("password", "oracle");
java.sql.Driver d =
Class.forName("oracle.jdbc.OracleDriver").newInstance();
java.sql.Connection conn =
Driver.connect("jdbc:oracle:thin:@172.24.146.88:1581/mani", props);

Web services,WSDL,SOAP

Web Service :
  • Web services are application components
  • Web services communicate using open protocols
  • Web services are self-contained and self-describing
  • Web services can be discovered using UDDI
  • Web services can be used by other applications
  • HTTP and XML is the basis for Web services

Web service Life Cycle :




A web service has the below six life-cycle events:

1. Service Provider creates the web service and deploys it.
2. Then service provider, publishes the information about a web service in a service registry.
3. Service consumer search a service registry for available services.
4. Service consumer retrieves the information about the service.
5. Service consumer creates a web service client.
6. Web service client invokes the web service at the location specified in the service description.

NOTE:- Its not mandatory to publish the web service information in a service registry, if the service provider knows the entire list of service consumers. They can directly provide the WSDL URL / file to service consumers.

WSDL :  Web Services Description Language


  • WSDL is written in XML
  • WSDL is an XML document
  • WSDL is used to describe Web services
  • WSDL is also used to locate Web services
  • WSDL is a W3C recommendation

SOAP :  Simple Object Access Protocol

  • SOAP is a communication protocol
  • SOAP is for communication between applications
  • SOAP is a format for sending messages
  • SOAP communicates via Internet
  • SOAP is platform independent
  • SOAP is language independent
  • SOAP is based on XML
  • SOAP is simple and extensible
  • SOAP allows you to get around firewalls
  • SOAP is a W3C recommendation


Timeout settings in SOA 11g

To increase the timeout in BPEL component, we need to remember following rule,
syncMaxWaitTime < BPEL EJB's transaction timeout < Global Transaction Timeout
Now,
1.How to set Global Transaction Timeout.
Go to weblogic console –> domain –>JTA tab.

image
2.How to set BPEL EJB's transaction timeout
Go to weblogic console—>deployment—>soa-infra—>ejb
Change the timeout of all bpel related ejb configuration,

image
3.How to set syncMaxWaitTime
Go to bpel properties from em console,

image
Go to more bpel configuration and in mbean increase the timeout value,

image

Oracle Weblogic Server Important Files Name, Locations and their Purpose

PATH For Admin Server
Purpose
Important Files Present
$DomainHome/$serverName/bin
Contains all the shell script files which is being used to start/stop and contains configuration for Admin and Managed servers.
setDomainEnv.sh
startWebLogic.sh
stopWebLogic.sh
$DomainHome/$serverName/config
Contains configuration files all important components e.g.  Domain configurtaion, JMS, JDBC etc
config.xml
jdbc config files
jms config files
fmwconfig files etc
$DomainHome/$serverName/osb/config
This directory mainly contains all the OSB artifats e.g. Proxy Services, business Services, XSD, Xquery etc, whatever we do from OSB console, most of stuff get store here only.
All the OSB artifacts
$DomainHome/$serverName/osb/config/core/_static/Ref_Store
This folder contains files having reference to OSB proxy and business services which are tagged with JMS as consumer. This directory helps during cleanup process of OSB deployment. There could be multiple OSB services get tagged with queue which could cause issues, this directory contents will help to clean that.
.str files for JMS MDB artifacts
$DomainHome/$serverName/sbgen
This folder contains MDBs for JMS queues, which could be used for any OSB Proxy service or JAVA application. 
ear files e.g. _ALSB_1341965872872.ear
$DomainHome/$serverName/sbgen/alsbTempJars
This folder contains the .jar files which Proxy services are using via JAVA Callout action.
jar files  e.g. tempCreateProcess8557633063030887848.jar
$DomainHome/$serverName/servers/$serverName/adr
Contains all diagnostic related data, if you have configured the Weblogic Diagnostic Framework e.g. In the event of server crash a report get generated etc, in this case a thread dumps file will generated here, also contains JMS, Datasource stats etc, good for investigation purpose.
jvm_threads.txt, dms_metrics.txt
$DomainHome/$serverName/servers/$serverName/data/store
This directory contains the persistent file store for weblogic servers which is used for normal functionality and diagnostic functionality. Weblogic has 7 internal components e.g. JMS Messages, JTA logs, EJB Timer services, Diagnostic services etc. which uses these persistent file store.
_WLS_$serverName000000.DAT
_WLS_DIAGNOSTICS000000.DAT
$DomainHome/$serverName/servers/$serverName/data/ldap
Contains LDAP related files, contains security realm details etc.  If you delete this folder, you will lose all security realm users details exist in Weblogic Admin console.
EmbeddedLDAP.data
changelog.data
changelog.index etc
$DomainHome/$serverName/servers/$serverName/data/console
Store the Admin console preference.
ConsolePreferences.xml
$DomainHome/$serverName/servers/$serverName/security
This file contains encrypted weblogic username and password, used while starting the server.
boot.properties
$DomainHome/$serverName/servers/$serverName/tmp
This folder contains all the artifacts which is been deployed in servers, alternatively can be seen from "deployment" section from Weblogic Admin Server console, included JMS MDB artifacts as well.
All the Library like this
adf.oracle.businesseditor
adf.oracle.domain etc
ALSB Logging
ALSB Publish
em
File Transport Provider components etc
$DomainHome/$serverName/servers/stage
This is stagging directory, during server startup process, JMS MDB, J2EE, War application get copied from Admin server to Managed server at this stage directory and then Managed server refer to local stage directory for deployment and things moved from Stage to 'tmp' directory. Note: for admin server you will not see this directory.
_ALSB_1352464196062 etc
$DomainHome/$serverName/servers/$serverName/logs
Contains all the logs files for troubleshooting purpose.
access.log,
AdminServer.log
ManagedServer.log
gc.log
domain.log
AdminServer.out
ManagedServer.out files
$DomainHome/$serverName/servers/sysman/log
Contains Management Service logs and trace file for troubleshooting purpose.
emoms.log
emoms.trc
$DomainHome/$serverName/servers/cache
Contains all the cached information weblogic uses directory to store cache for various components e.g. web tire related cache, JMS cache, data sources, EJB cache etc.
.class files

What is Oracle SOA ?

Oracle SOA Suite is a comprehensive, hot-pluggable software suite to build, deploy and manage Service-Oriented Architectures (SOA). The components of the suite benefit from common capabilities including consistent tooling, a single deployment and management model, end-to-end security and unified metadata management. Oracle SOA Suite's hot-pluggable architecture helps businesses lower upfront costs by allowing maximum re-use of existing IT investments and assets, regardless of the environment (OS, application server, etc.) they run in, or the technology they were built upon. Its easy-to-use, re-use focused, unified application development tooling and end-to-end lifecycle management support further reduces development and maintenance cost and complexity.

Checking Socket and Servlet Mode in EBS 11i/R12

 How to check whether the Oracle Forms server is running in servlet or socket mode ?



Oracle Applications Release 12
Note Oracle Application Release 12 is, by default, configured to run in servlet mode.
Use the following command:
$ grep connectMode FORMS_WEB_CONFIG_FILE
The current connection mode is reported:
connectMode=servlet
Alternatively, use the following command:
$ grep_frmConnectMode CONTEXT_FILE
The current connection mode is reported:
<forms_connect oa_var="s_frmConnectMode">servlet</forms_conr....

Oracle Applications Release 11
Note Oracle Application Release 11 is, by default, configured to run in socket mode.
Use the following command:
$ grep connectMode FORMS60_WEB_CONFIG_FILE
The current connection mode is reported:
connectMode=socket
Alternatively, use the following command:
$ grep socket CONTEXT_FILE
The current connection mode is reported:

<forms_connect oa_var="s_frmConnectMode">socket</forms_conr....


Checking the HTML Source [ from front end ]  : 

Interview Question : How to check forms mode from front end ?

To do so with Internet Explorer, select View, and then Source.




Description of Figure A-1 follows