MDS-01330: unable to load MDS configuration document
My whole SOA env was down
Error Message in logs :
MDS-01330: unable to load MDS configuration document
MDS-01329: unable to load element "persistence-config"
MDS-01370: MetadataStore configuration for metadata-store-usage "OWSM_TargetRepos" is invalid.
MDS-00922: The ConnectionManager "oracle.mds.internal.persistence.db.JNDIConnectionManagerImpl" cannot be instantiated.
weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: ORA-28001: the password has expired
Cause :
The reason for this is that the passwords used by SOA (with its different users) to access the Database have expired
Solution:
1.Log in to SQLPLUS with system as sysdba [ If you dont have access ask your DBA guys to perform these tasks ]
2.Run the below Query to see the schemas that present in your repository
SET linesize 120
SET pagesize 1000
col owner FORMAT a20
col comp_name FORMAT a40
col version FORMAT a12
SELECT owner, comp_name, version, status, upgraded
FROM schema_version_registry
ORDER BY 1, 2, 3;
[You should change the passwords to all schemas that have the OWNER beginning with outdated "Prefix", Prefix refers to the related prefix used for your SOA schemas.]
3. change DB Pwd using
ALTER USER <user_name> identified BY <new_password>;
4. Log in to weblogic console and go to "Domain Structure/Services/Data Source" to change password to new one in Connection Pool tab.Do it for mds-owsm, mds-soa, OraSDPMDataSource, SOADataSource, and SOALocalTxDataSource.
5.Restart all the services in right order.
Error Message in logs :
MDS-01330: unable to load MDS configuration document
MDS-01329: unable to load element "persistence-config"
MDS-01370: MetadataStore configuration for metadata-store-usage "OWSM_TargetRepos" is invalid.
MDS-00922: The ConnectionManager "oracle.mds.internal.persistence.db.JNDIConnectionManagerImpl" cannot be instantiated.
weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: ORA-28001: the password has expired
Cause :
The reason for this is that the passwords used by SOA (with its different users) to access the Database have expired
Solution:
1.Log in to SQLPLUS with system as sysdba [ If you dont have access ask your DBA guys to perform these tasks ]
2.Run the below Query to see the schemas that present in your repository
SET linesize 120
SET pagesize 1000
col owner FORMAT a20
col comp_name FORMAT a40
col version FORMAT a12
SELECT owner, comp_name, version, status, upgraded
FROM schema_version_registry
ORDER BY 1, 2, 3;
[You should change the passwords to all schemas that have the OWNER beginning with outdated "Prefix", Prefix refers to the related prefix used for your SOA schemas.]
3. change DB Pwd using
ALTER USER <user_name> identified BY <new_password>;
4. Log in to weblogic console and go to "Domain Structure/Services/Data Source" to change password to new one in Connection Pool tab.Do it for mds-owsm, mds-soa, OraSDPMDataSource, SOADataSource, and SOALocalTxDataSource.
5.Restart all the services in right order.
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.Run the configuration script "setWLSEnv.sh" first.
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:
- Look at the Server Logs...related to JDBC information.
- Try to use the "utils.dbping" utility provided by WebLogic to test the connectivity between target Server Box and the Database.
- 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);
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 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
- 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.
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,
3.How to set syncMaxWaitTime
Go to bpel properties from em console,
Go to more bpel configuration and in mbean increase the timeout value,
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
|
Subscribe to:
Posts (Atom)