Directlink to BPEL Engine - Recovery from EM

Hi,
Since the Enterprise Manager GUI can be horribly slow i'm trying to figure out what direct URLs to use on login.
I have URLs for the different soa infra pages, such as instances, faults and rejected messages etc, but i cannot figure out the URLs to "BPEL Engine" tabs.
I can get to the BPEL Engine dashboard directly on login with
https://host:port/em/faces/ai/soa/bpelEngine?target=/Farm_Domain/Domain/Domain_S2/soa-infra&type=oracle_soainfra
Any idea to get a similar link that gets me direct to the Recovery tab?
The pattern to get direct-links under soa-infra is as follows:
https://host:port/em/faces/ai/soa/infra?target=/Farm_Domain/Domain/Domain_S2/soa-infra&type=oracle_soainfra&selectedTab=instancesTab
https://host:port/em/faces/ai/soa/infra?target=/Farm_Domain/Domain/Domain_S2/soa-infra&type=oracle_soainfra&selectedTab=faultsTab
etc.

Lucky , today
I find it after try to search in EM.
Here is my way :
EM>Farm_soa_domain>weblogic domain>your_domain>soa_server1>right click menu>system Mbean browser>oracle.soa.config>server:soa_server1>SCAComposite>your project> SCAComposite.SCAComponent>processName>
Click the properties attribute , then goes to a tableview, you will see all properties you set in design time. you will be able to change as well.
Cheers
Kevin

Similar Messages

Backup/Recovery from web application

Hello guys,
I am using Oracle 9i as DB and Oracle 9iAS for web application server. I want to provide Backup and Recovery functionality to the user via web. I don't know any thing in this regard.
Is it possible that we can take backup and recovery from web application?
Is there any alternative for this function.
any other comments will be appreciated.
Thank you,
Jawed Nazar Ali

Read this article in order to get an idea about Java Stored Procedures.
Oracle Developer JAVA STORED PROCEDURES
Simplify with Java Stored Procedures
By Kuassi Mensah
Use Java stored procedures to bridge SQL, XML, Java, and J2EE and Web Services.
Stored procedures allow a clean separation of persistence logic that runs in the database tier from business logic that runs in the middle tier. This separation reduces overall application complexity and increases reuse, security, performance, and scalability.
A major obstacle, however, for widespread adoption of stored procedures is the set of various proprietary, database-dependent implementation languages that different database vendors use. The use of Java-based stored procedures fixes this concern. Oracle has implemented ANSI standards that specify the ability to invoke static Java methods from SQL as procedures or functions. This implementation is called simply "Java stored procedures."
In this article, you will learn how Java stored procedures help simplify and increase the performance of your business logic and extend database functionality. I'll show how Oracle enables the use of Java stored procedures within the database. I'll also look at how Java stored procedures access data, and show how to create a basic Java stored procedure.
PL/SQL or Java
When you think of Oracle stored procedures, you probably think of PL/SQL. Oracle, however, has provided Java support in the database since Oracle8i, to offer an open and portable alternative to PL/SQL for stored procedures. I can hear the $64,000 question: "How do I choose between PL/SQL and Java? Should I forget all the things I've been told about PL/SQL and move on to the greener Java pastures?"
Both languages are suitable for database programming, and each has its strengths and weaknesses. In deciding which language to use, here's a general rule of thumb:
Use PL/SQL for database-centric logic that requires seamless integration with SQL and therefore complete access to database objects, types, and features.
Use Java as an open alternative to PL/SQL for database independence, but also for integrating and bridging the worlds of SQL, XML, J2EE, and Web services.
OracleJVM Lets You Run Java within the Database
Since Oracle8i, Release 1 (Oracle 8.1.5), Oracle has offered a tightly integrated Java virtual machine (JVM) that supports Oracle's database session architecture. Any database session may activate a virtually dedicated JVM during the first Java code invocation; subsequent users then benefit from this already Java-enabled session. In reality, all sessions share the same JVM code and staticsonly private states are kept and garbage collected in an individual session space, to provide Java sessions the same session isolation and data integrity capabilities as SQL operations. There is no need for a separate Java-enabled process for data integrity. This session-based architecture provides a small memory footprint and gives OracleJVM the same linear SMP scalability as the Oracle database.
Creating Java Stored Procedures
There are a few steps involved in turning a Java method into a Java stored procedure. These include loading the Java class into the database using the loadjava utility, and publishing the Java methods using a call specification (Call Spec) to map Java methods, parameter types, and return types to their SQL counterparts. The following section shows how to do this.
I'll use a simple Hello class, with one method, Hello.world(), that returns the string "Hello world":
public class Hello
public static String world ()
return "Hello world";
The Loadjava Utility
Loadjava is a utility for loading Java source files, Java class files, and Java resource files; verifying bytecodes; and deploying Java classes and JAR files into the database. It is invoked either from the command line or through the loadjava() method contained within the DBMS_JAVA class. To load our Hello.class example, type:
loadjava -user scott/tiger Hello.class
As of Oracle9i Release 2, loadjava allows you to automatically publish Java classes as stored procedures by creating the corresponding Call Specs for methods contained in the processed classes. Oracle provides Oracle9i JDeveloper for developing, testing, debugging, and deploying Java stored procedures.
The Resolver Spec
The JDK-based JVM looks for and resolves class references within the directories listed in the CLASSPATH. Because Oracle database classes live in the database schema, the OracleJVM uses a database resolver to look for and resolve class references through the schemas listed in the Resolver Spec. Unlike the CLASSPATH, which applies to all classes, the Resolver Spec is applied on a per-class basis. The default resolver looks for classes first in the schema in which the class is loaded and then for classes with public synonyms.
loadjava -resolve <myclass>
You may need to specify different resolvers, and you can force resolution to occur when you use loadjava, to determine at deployment time any problems that may occur later at runtime.
loadjava -resolve -resolver "((* SCOTT) (foo/bar/* OTHERS)
(* PUBLIC))"
Call Spec and Stored Procedures Invocation
To invoke a Java method from SQL (as well as from PL/SQL and JDBC), you must first publish the public static method through a Call Spec, which defines for SQL the arguments the method takes and the SQL types it returns.
In our example, we'll use SQL*Plus to connect to the database and define a top-level Call Spec for Hello.world():
SQL> connect scott/tiger
SQL> create or replace function helloworld return
VARCHAR2 as language java name 'Hello.world () return
java.lang.String';
Function created.
You can then invoke the Java stored procedure as shown below:
SQL> variable myString varchar2[20];
SQL> call helloworld() into :myString;
Call completed.
SQL> print myString;
MYSTRING
Hello world
Java stored procedures are callable, through their Call Spec, from SQL DML statements (INSERT, UPDATE, DELETE, SELECT, CALL, EXPLAIN PLAN, LOCK TABLE, and MERGE), PL/SQL blocks, subprograms, and packages, as well as database triggers. The beauty of Call Spec is that stored procedure implementations can change over time from PL/SQL to Java or vice versa, transparently to the requesters.
Call Spec abstracts the call interface from the implementation language (PL/SQL or Java) and therefore enables sharing business logic between legacy applications and newer Java/J2EE-based applications. At times, however, when invoking a database-resident Java class from a Java client, you may not want to go through the PL/SQL wrapper. In a future release, Oracle plans to provide a mechanism that will allow developers to bypass the Call Spec.
Advanced Data-Access Control
Java stored procedures can be used to control and restrict access to Oracle data by allowing users to manipulate the data only through stored procedures that execute under their invoker's privileges while denying access to the table itself. For example, you can disable updates during certain hours or give managers the ability to query salary data but not update it, or log all access and notify a security service.
Sharing Data Logic Between Legacy and J2EE Applications
Because legacy applications and J2EE applications both invoke stored procedures through the Call Spec, the same data logic can be shared between J2EE and non-J2EE worlds. Thanks to Call Spec, this data logic can be shared regardless of the implementation language used (whether PL/SQL or Java).
Autogeneration of Primary Keys for BMP Entity Beans
When using BMP for EJB entity beans, a bean instance can be uniquely identified by the auto-generated primary key associated with the newly inserted data as a return value for ejbCreate(). You can retrieve this value within ejbCreate() in one database operation by using a stored procedure that inserts the corresponding data and retrieves or computes the primary key. Alternatively, you could insert the data and retrieve the corresponding key (or ROWID) in one SQL statement, using the RETURN_GENERATED_KEYS feature in JDBC 3.0. However, the stored procedure approach is more portable across JDBC driver versions and databases.
You can implement this pattern with these three steps:
Create the Java stored procedure, defining a public static Java method insertAccount() within a public GenPK class. This method will insert data, compute a unique key (by passing out a sequence number), and return the computed key as primary key.
Define the Call Spec.
CREATE OR REPLACE PROCEDURE insertAccount(owner IN
varchar, bal IN number, newid OUT number)
AS LANGUAGE JAVA NAME 'GenPK.insertAccount(
java.lang.String [])';
Invoke the stored procedure within ejbCreate().
Public AccountPK ejbCreate(String ownerName, int balance) throws CreateException
try {
CallableStatement call = conn.prepareCall{
"{call insertAccount(?, ?, ?)}"};
return new AccountPK(accountID);
Custom Primary Key Finders for CMP Entity Beans
Finder methods are used for retrieving existing EJB entity bean instances. Primary key finders allow you to retrieve a uniquely identified EJB instance. For CMP entity beans, the EJB container automatically generates the primary key finder findByPrimaryKey() method, based on declarative description. In some situations, however, you might need more control; for example, you may need a specialized finder such as findByStoredProcKey(). In these situations, you can use Java stored procedures in conjunction with an object relational framework (such as Oracle9i Application Server [Oracle9iAS] TopLink) to implement a custom primary key finder method. After you define the EJB finder as a REDIRECT or NAMED finder, TopLink will generate the SQL query for retrieving the bean instance.
Data-Driven EJB Invocation
In a data-driven architecture, business logic invocation can be triggered as a result of database operations (such as inserts, updates, or deletes). A Java stored procedure implementing the data logic can be declared as a database trigger to invoke EJBs running in a middle-tier J2EE application server. You can make EJB calls by using either standard remote method invocation (RMI) over Interoperable Inter-ORB Protocol (IIOP), using a J2EE 1.3 compatible server, or RMI over a vendor-specific transport protocol (such as ORMI with Oracle9iAS/OC4J or RMI over T3 with BEA WebLogic). Each application server vendor has its own optimized protocol while providing RMI over IIOP for interoperability. Oracle9iAS supports both RMI calls over IIOP and ORMI protocols.
Data-Driven Messaging
Oracle9i Database embeds Advanced Queuing (AQ), which is an integrated, persistent, reliable, secure, scalable, and transactional message-queuing framework. Oracle exposes AQ features to Java developers through the standard Java Messaging System (JMS) API. Java stored procedures can invoke AQ operations through the JMS interface to allow fast, intra-session, scalable, data-driven messaging.
Java stored procedures can use JMS to invoke AQ operations. You can implement this pattern in four steps:
Create and start the JMS Queue (to do so, embed the following operations within a SQL script):
execute dbms_aqadm.create_queue_table(queue_table =>
'queue1', queue_payload_type =>
'SYS.AQ$_JMS_TEXT_MESSAGE', comment => 'a test queue',
multiple_consumers => false, compatible => '8.1.0');
execute dbms_aqadm.create_queue( queue_name => 'queue1',
queue_table => 'queue1' );
execute dbms_aqadm.start_queue(queue_name => 'queue1');
Create the Java stored procedure (a code snippet is shown):
public static void runTest(String msgBody)
try
// get database connection
ora_drv = new OracleDriver();
db_conn = ora_drv.defaultConnection();
// setup sender (cf online code sample)
// create message
s_msg = s_session.createTextMessage(msgBody);
// send message
sender.send(s_msg);
s_session.commit();
// receive message
r_msg = (TextMessage) receiver.receive();
r_session.commit();
// output message text
String body = r_msg.getText();
System.out.println("message was '"+body+"'");
Create the Call Spec:
create or replace procedure jmsproc (t1 IN VARCHAR)
as language java name 'jmsSample.main (java.lang.String[])';
Invoke the stored procedure:
call jmsproc('hello');
Database-Assisted Web Publishing (Cache Invalidation)
One of the common issues application architects must face is how to cache database information reliably to increase overall system performance. JCACHE is an upcoming standard specification (JSR 107) that addresses this problem. It specifies an approach for temporary, in-memory caching of Java objects, including object creation, shared access, spooling, invalidation, and consistency across JVMs. It can be used to cache read-mostly data such as product catalogs and price lists within JSP. Using JCACHE, most queries will have response times an order of magnitude faster because of cached data (in-house testing showed response times about 15 times faster).
In order to track all the changes to the origin data and refresh the cached data, a Java stored procedure is attached to a table as a trigger. Any change to this table will result in the automatic invocation of this stored procedure, which in turn will call out a defined JSP to invalidate the JCACHE object that maps its state to the database table. Upon invalidation, the very next query will force the cache to be refreshed from the database. Next Steps
READ MORE about Java Stored Procedures
This article is adapted from the white paper "Unleash the Power of Java Stored Procedures." You can find the white paper at:
/tech/java/java_db/pdf/
OW_30820_JAVA_STORED_PROC_paper.PDF
New PL/SQL features in Oracle9i Database, Release 2
/tech/pl_sql/pdf/
Paper_30720_Doc.pdf
Resolver Spec
/docs/products/oracle9i/
doc_library/release2/java.920/a96659.pdf
OracleJVM and Java 2 Security
/docs/products/oracle9i/
doc_library/release2/java.920/a96656.pdf
DOWNLOAD Code
Exercise code examples from this article:
/sample_code/tech/
java/jsp/Oracle9iJSPSamples.html
LEARN about stored procedures as Web services
/tech/webservices
Extending Database Functionality
One of the great things about running Java code directly in the database is the ability to implement new functionality by simply loading the code or library and using the Call Spec to make the entry points (public static methods) available to SQL, PL/SQL, Java, J2EE, and non-Java APIs. Oracle9i Database customers can easily extend database functionality. Oracle itself leverages this capability for new utilities and packages such as the XML Developer Kits (XDKs).
Bridging SQL, PL/SQL, Java, J2EE, .NET, and XML
The Oracle XDK is written in Java and exposes its public methods as Java stored procedures, extending the database's XML programmability. SQL, PL/SQL, Java, J2EE, and non-Java (.NET) business logic all have access to the XML parser, the XSLT processor, the XPath engine, and XML SQL Utility (XSU).
The XML parser is accessible through the xmlparser and xmldom packages. XSU is a Java utility that generates an XML document from SQL queries or a JDBC ResultSet, and writes data from an XML document into a database table or view. Using XSU, XML output can be produced as Text, DOM trees, or DTDs. XSU is exposed to PL/SQL through the dbms_xmlquery and dbms_xmlsave packages.
Conclusion
The integration of the Oracle database with a Java VM enables the creation of portable, powerful, database-independent data logic and persistence logic. The loose coupling of business logic that runs in the middle tier with data logic that runs in the database tier improves application scalability, performance, flexibility, and maintenance.
Kuassi Mensah ([email protected]) is a product manager in the Server Technologies division at Oracle.
http://otn.oracle.com/oramag/oracle/03-jan/o13java.html
Joel Pérez

Wait on the Database Engine recovery handle failed. Check the SQL server error log for potential causes in SQL Server 2012 Developer Edition

I m using SQL Server 2012 Developer Edition. Even I tried 2012 express and enterprise edition but all
gave same error. I browsed msdn blog. But nothing help me out.
Below is the error log details--
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2013-10-21 12:58:05
End time: 2013-10-21 13:52:30
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for RS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for DQ: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for FullText: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: CROY-TOSH
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: C:\Users\CRoy\Downloads\SQL Server 2012 Developer Edition (x86 and x64) - DVD (English)\x64\setup\
Installation edition: Developer
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLSERVERAGENT
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AI
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: NT Service\MSSQLServerOLAPService
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: CRoy-TOSH\CRoy
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: ROY
CLTRESULTDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir\
CLTSTARTUPTYPE: Manual
CLTSVCACCOUNT: NT Service\SQL Server Distributed Replay Client
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
CTLRSTARTUPTYPE: Manual
CTLRSVCACCOUNT: NT Service\SQL Server Distributed Replay Controller
CTLRSVCPASSWORD: <empty>
CTLRUSERS: CRoy-TOSH\CRoy
ENABLERANU: false
ENU: true
ERRORREPORTING: true
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK, MDS
FILESTREAMLEVEL: 2
FILESTREAMSHARENAME: MSSQLSERVER
FTSVCACCOUNT: NT Service\MSSQLFDLauncher
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT Service\MsDtsServer110
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: SharePointFilesOnlyMode
RSSVCACCOUNT: NT Service\ReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AI
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: CRoy-TOSH\CRoy
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Passed
Feature: Client Tools Connectivity
Status: Passed
Feature: Client Tools SDK
Status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
Feature: Management Tools - Basic
Status: Passed
Feature: SQL Server Data Tools
Status: Passed
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Data Quality Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Master Data Services
Status: Passed
Feature: Distributed Replay Client
Status: Passed
Feature: Distributed Replay Controller
Status: Passed
Feature: Integration Services
Status: Passed
Feature: Data Quality Client
Status: Passed
Feature: Analysis Services
Status: Passed
Feature: Reporting Services - SharePoint
Status: Passed
Feature: Reporting Services Add-in for SharePoint Products
Status: Passed
Feature: SQL Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\SystemConfigurationCheck_Report.htm

Hi,
This 3rd time I followed this link. But nothing new, same error.
Can you please tell me how to do follow, I cannt do the 1st step, how to change the local system to windows level account, vice-versa. It is shown mine as
Server Configuration Manager(Local)
From here I folllowed the steps ---[I cannt insert link/image :-(]
SQL 2008/R2 setup fails with "Wait on the database engine recovery handle failed"
If I right clicked on SQL Server Service, there is no option to change the account.
Hello,
Thanks for your patience,did you tried stesp mentioned in below article
http://blogs.msdn.com/b/sqljourney/archive/2012/03/16/sql-2008-r2-setup-fails-with-quot-wait-on-the-database-engine-recovery-handle-failed-quot.aspx
To resolve it, follow these steps:-
When the installation throws this error, click on OK and allow it to proceed. It will fail for Database Engine, but the SQL Server service should have
been created. Check the Services console.
If the service is present, perform the following steps:-
1. Go to SQL Server Configuration manager, right click on the SQL Server service, and change the service account (if it is local system, give
it a windows level account, and vice-versa). It might throw a WMI error but you will see the account getting updated anyway. If not, then use the Services console. Change the account for SQL Agent as well.
Use this link to change sql server service account
http://technet.microsoft.com/en-us/library/ms345578.aspx
2. Next, try to start the service. It should come online.
3. However, you will not be able to log in to the SQL Server
4. Now stop the service and start it from the command prompt using -m -c -T3608 parameters.
5. Now try logging in to the server using admin connection from sqlcmd (sqlcmd admin:<server name>\<instance name> ...)
6. Once logged in, use the sp_addsrvrolemember '<domain\username>','sysadmin'.
Also add the builtin/administrators to the sysadmin role
7. Now stop the service from the command prompt and start it from SQL Server configuration manager
You should be able to log in to the server now.
Hope this helps someone.
Please revert if it helps or even if it does not
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

BPEL Message Recovery Required

Hi Friends,
while execute the Database to Database BPEL process i encountered the below exception. can you please any one let me know, at what situation we may get this type of exceptions and how can we overcome it.
BPEL Message Recovery Required
This flowtrace contains BPEL messages pending recovery. To view and recover these messages, navigate to the Recovery tab on the BPEL Service Engine home page.
Invoke 1
Callback 0
Activity 0
To locate these messages in the BPEL Recovery tab, select message type and filter by this ECID:
11d1def534ea1be0:6e77e19a:132905ba474:-8000-00000000000005b4
Thanks,
Hari

We have an option in the EM console to retry all faults for a composite by setting some values in custom MBeans. They are available as Advanced BPEL properties in the SOA Infra engine.
The MBean that allows recovery of faulted instances is RecoveryConfig. It has two options for retrying
RecurringScheduleConfig : A recovery window may be specified (most probably off peak hours) to recover all faulted instances. Messages being recovered can be throttled by limiting the number of messages picked up on each run by specifying the maxMessageRaiseSize.
StartupScheduleConfig : With this setting on all faulted instances are automatically retried when the soa server is booted up for restart.
More details on how to use RecoverConfig Mbean can be found here
http://download.oracle.com/docs/cd/E14571_01/relnotes.1111/e10133/soa.htm#RNLIN1052

BPMN vs BPEL engine

hi
Just want to know about BPMN and BPEL execution,
what is the diff in execution? from performance perspective which is considered better?
i know BPMN and BPEL engines are there for execution for BPMN and BPEL and they both share same logging, auditing, instance hydration and dehydration and routing services.
But still is there anything that gets executed behind the scenes between BPMN and BPEL? and is any component has better perfomance in terms of execution,
Just in case assume same project is implemented in both BPMN and BPEL and executed, is there any performance factor associated?

The primary purpose of BPMN spec is meant to have a standard visual notation for business process diagram that can be understood by both business users and IT users. and in my view, the purpose of XPDL now is primarily used to be a standard serialization (interchange) format for exchanging BPMN models. BPMN does have all properties needed for generating executable BPEL. But BPMN is a visual graphic flow language and is more expressible than BPEL - not all BPMN flows can be expressed in BPEL and the mapping is non trivial. Having an XML execution language using BPMN seems too much and would cause serious problems in terms of portablity.
If you are interested in knowing more about BPMN-BPEL mapping, you can take a look at business process modeling info from http://www.eclarus.com. It contains good information on BPMN and BPMN-BPEL mapping.
Hong-Lee

Make a BPEL instance recoverable from a BPEL fault hanler?

Hi
Does anybody know of a way to make a BPEL instance recoverable from a BPEL catch fault handler, e.g. using Java to programatically instruct the service engine to do the same thing as when using the fault management framework and fault policies to perform a human-intervention action?
A scenario where this would be very useful is when you have a transformation that fails, e.g. due to missing values in a DVM or XREF. Then, instead of having to do a resend from the source system, you would solve the issue in the affected DVM or XREF and then recover the instance.
Regards
Lars

Hi,
I don't know of an expiclit way of achieving this directly from within a BPEL Fault handler (e.g. Java API Calls). However an approach i have used is to be a little creative with the use of additional components. You could either place the xForm in a spearate component. Thay way be invoking from the parent component the invoke will receive the fault. Hence your fault framework and fault policies can configure the appropraite actions beacuse the fault occurs on an invoke. Another approach is if you did not want to move the transform is to call a spearate component that just throws a fault. This would have a similar approach as the invoke would receive the fault.
Regards Dave

Sun BPEL engine sets wrong Content-Type on calling an external web service

I have a WSDL for an external web service (which as it happens is running in Websphere locally) and have implemented it as a
partnerlink on a BPEL diagram in an SOA composite project. The binding style is Document and if you use SOAPUI to test it it
works fine. Tracing on the web service's server shows the SOAP request coming in. It has a content-type of text/xml, as expected. If I do a JUnit test from NetBeans based on this WSDL alone it also works - same result. BUT if I do
a full test and call my BPEL process the invocation of this service from BPEL fails.
On the Test result you see
BPCOR-6135:A fault was not handled in the process scope; Fault Name is http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault;
(This happens because I did not handle the fault in the BPEL.)
On the trace I see it now has Content-type of application/xop+xml. Why would the Sun BPEL engine change this? I just
accepted the usual defaults when I created the PartnerLink and the Invoke. Anyway, the format of the request doesn't match what the WS server expects, so it fails.
As far as I'm aware I'm just using SOAP1.1. This is NetBeans 6.5 with Glassfish 2.1. I tried with NetBeans 6.7 and it got worse, not better. I would certainly appreciate any advice?
Thanks

Perhaps when the BPEL file based process calls the WSDL file to execute,their message communication is not correct.
the head part in the WSDL file should be manually set to "text/xml", or the IDE or Server will use the default value;
for example as follow:
SOAPUI tool would use the default value "text/xml" to request.(depends the tool support).
NetBeans tool would use the default value "text/xml" to request.
when you do a full test and you do not set the head "context-type" value ,the WSDL file use the server's default head
value"application/xop-xml" so that return the contents under the control of the server's default value.
I hope these will be useful for you.

BPEL engine sets wrong Content-Type on calling an external web service

I have a WSDL for an external web service (which as it happens is running in Websphere locally) and have implemented it as a
partnerlink on a BPEL diagram in an SOA composite project.
The binding style is Document and if you use SOAPUI to test it it
works fine. Tracing on the web service's server shows the SOAP request
coming in. It has a content-type of text/xml, as expected. If I do a
JUnit test from NetBeans based on this WSDL alone it also works - same result. BUT if I do
a full test and call my BPEL process the invocation of this service
from BPEL fails.
On the Test result you see
BPCOR-6135:A fault was not handled in the process scope; Fault Name is http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault;
(This happens because I did not handle the fault in the BPEL.)
On the trace I see it now has Content-type of
application/xop+xml. Why would the Sun BPEL engine change this? I just
accepted the usual defaults when I created the PartnerLink and the
Invoke. Anyway, the format of the request doesn't match what the WS server expects, so it fails.
As far as I'm aware I'm just using SOAP1.1. This is NetBeans 6.5 with
Glassfish 2.1. I tried with NetBeans 6.7 and it got worse, not better.
I would certainly appreciate any advice?
Thanks

Perhaps when the BPEL file based process calls the WSDL file to execute,their message communication is not correct.
the head part in the WSDL file should be manually set to "text/xml", or the IDE or Server will use the default value;
for example as follow:
SOAPUI tool would use the default value "text/xml" to request.(depends the tool support).
NetBeans tool would use the default value "text/xml" to request.
when you do a full test and you do not set the head "context-type" value ,the WSDL file use the server's default head
value"application/xop-xml" so that return the contents under the control of the server's default value.
I hope these will be useful for you.

BPEL Manual Recovery

I am using SOA 11g. I have a one way bpel process starting from JMS Consumer till a file adaoter write. On any catchall scenario, the instance goes to manual recovery and the state of the instance shows as "Running" and this state remains for a long time. Any suggestions to over come this?

Arik,
On a selection fault which is not handled out of seedeed faults, it is going to catchall block. In catch all block, I am having an assign for AIAAsyncErrorHandlingBpelProcess variable and invoke to AIAASyncErrorHandlingBpelProcess followed by throw which throws the AIAAsync Input variable. So at runtime, the selection fault is leading the process to catchall and the isntance shows as faulted since we have throw but the process state shows Running and goes to manual recovery. Can you please suggest on this.

BPEL manual recovery - 10.1.3.3

Hi,
We have some stuck processes in our BPEL manual recovery console.
We have tried recovering messages from the console itself. However they still dont to disappear and create an instance.
I dont see anything in the logs as well.
Can you please help in getting the messages? ALso, is the payload stored anywhere?
Version is 10.1.3.3
Thanks,
Rosh

On BPEL Console, select your domain. Go To Configuration --> Logging and increase the logging level, preferably to All or DEBUG. Now try to recover and check if you find anything in logs.
On the Manual Recovery (invoke/recv/activity), when you click on conversation Id, are you able to see the right payload ?

BPEL Engine XPATH (non?) compliance

Hi,
what is the level of compliance of BPEL Engine 10.1.3.4 (MLR#8) to XPATH 1.0 or XPATH 2.0?
Specifically, I am interested in boolean() function. XPATH 1.0 and XPATH 2.0 specifications both state the following:
http://www.w3.org/TR/xpath/#function-boolean
>
Function: boolean boolean(object)
The boolean function converts its argument to a boolean as follows:
* a number is true if and only if it is neither positive or negative zero nor NaN
* a node-set is true if and only if it is non-empty
* a string is true if and only if its length is non-zero
* an object of a type other than the four basic types is converted to a boolean in a way that is dependent on that type
>
http://www.w3.org/TR/xpath-functions/#func-boolean
>
15.1.1 fn:boolean
fn:boolean($arg as item()*) as xs:boolean
Summary: Computes the effective boolean value of the sequence $arg. See Section 2.4.3 Effective Boolean ValueXP
* If $arg is the empty sequence, fn:boolean returns false.
* If $arg is a sequence whose first item is a node, fn:boolean returns true.
* If $arg is a singleton value of type xs:boolean or a derived from xs:boolean, fn:boolean returns $arg.
* If $arg is a singleton value of type xs:string or a type derived from xs:string, xs:anyURI or a type derived from xs:anyURI or xs:untypedAtomic, fn:boolean returns false if the operand value has zero length; otherwise it returns true.
* If $arg is a singleton value of any numeric type or a type derived from a numeric type, fn:boolean returns false if the operand value is NaN or is numerically equal to zero; otherwise it returns true.
* In all other cases, fn:boolean raises a type error [err:FORG0006].
>
In bpel, if I have a switch with a case expression as boolean(bpws:getVariableData('inputVariable','payload','/client:TestRequest/client:StringValue')), this returns false only if the StringValue element is missing in the inputVariable payload. If the StringValue element is present but is empty like <stringElement/>, then this expression returns true.
Is this a bug?
Thanks,
Shanmu.

bumping up to check if some one can provide more information
Regards,
Shanmu.

Learning the internals of BPEL engine

I want to understand how the bpel engine handles a request. More specifically, from the time it gets a request to the time it instantiate the correct bpel process, what are the steps involved. Where can I find some documentation on this. I looked at the BPEL dev guide (10.1.3.1) and admin guide...but this info does not seems to be there...any pointers

Resubmitting...

BPEL invocation securely from client using JAZN security not working.

HI,
We are trying to invoke the BPEL process securely from the client application using JAZN security settings, this is not working, with any credentilas or with out providing the security credentilas BPEL invocation is happening. Need the solution for this security credentials while invoking the BPEL process.
Please provide the update at the earliest. Thanks in advance. Your quick update is greatly appreciated.

Hi James,
Thanks for the update.
Please find the attached docs.
Bpel.xml:
<?xml version = '1.0' encoding = 'UTF-8'?>
<BPELSuitcase>
<BPELProcess id="HelloWorld" src="HelloWorld.bpel">
<partnerLinkBindings>
<partnerLinkBinding name="client">
<property name="wsdlLocation">HelloWorld.wsdl</property>
</partnerLinkBinding>
</partnerLinkBindings>
<configurations>
<property name="role">oc4j-administrators</property>
</configurations>
</BPELProcess>
</BPELSuitcase>
orion-application.xml: folder location: C:\product1\10.1.3.1\OracleAS_1\j2ee\home\applications\orabpel\META-INF\orion-application.xml
<?xml version="1.0"?>
<orion-application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/orion-application-10_0.xsd"
schema-major-version="10"
schema-minor-version="0" component-classification="internal-BPEL">
<connectors path="./oc4j-connectors.xml"/>
     <ejb-module remote="false" path="ejb_ob_engine.jar" />
     <ejb-module remote="false" path="ejb_services.jar" />
     <web-module id="httpbinding" path="httpbinding.war" />
     <web-module id="admin_war" path="admin_war" />
     <web-module id="startup_war" path="startup_war" />
     <web-module id="console_war" path="console_war" />
     <persistence path="persistence" />
     <principals path="principals.xml" />
     <jazn provider="XML" location="../../config/system-jazn-data.xml" jaas-mode="doAsPrivileged">
     
</jazn>
<imported-shared-libraries>
     <inherited-shared-libraries/>
     <import-shared-library name="oracle.bpel.common" parent="api" />
     <import-shared-library name="oracle.ws.client" parent="oracle.ws.jaxrpc" version="10.1.3" />
     <import-shared-library name="oracle.ws.jaxrpc" />
     <import-shared-library name="oracle.toplink" />
     <import-shared-library name="oracle.ws.testpage" />
     </imported-shared-libraries>
     <log>
          <file path="application.log" />
     </log>
     <namespace-access>
          <read-access>
               <namespace-resource root="">
                    <security-role-mapping name="oc4j-administrators">
                         <group name="oc4j-administrators" />
                    </security-role-mapping>
               </namespace-resource>
          </read-access>
          <write-access>
               <namespace-resource root="">
                    <security-role-mapping name="oc4j-administrators">
                         <group name="oc4j-administrators" />
                    </security-role-mapping>
               </namespace-resource>
          </write-access>
     </namespace-access>
     <security-role-mapping name="PUBLIC">
          <group name="{{PUBLIC}}" />
     </security-role-mapping>
</orion-application>
web.xml file: C:\product1\10.1.3.1\OracleAS_1\j2ee\home\applications\orabpel\startup\WEB-INF\web.xml
<?xml version="1.0" ?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app id="StartupWebApp_Id">

<servlet id="BPEL_OC4J_Servlet_Id">
<servlet-name>BPEL_OC4J_Servlet</servlet-name>
<display-name>BPEL OC4J JAX/RPC Servlet</display-name>
<description>BPEL endpoint Provider Port via oc4j jax/rpc</description>
<servlet-class>com.collaxa.cube.ws.soap.oc4j.BPELOC4JServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet id="LoaderServlet_Id">
<servlet-name>cxloader</servlet-name>
<servlet-class>com.collaxa.cube.admin.CXLoaderServlet</servlet-class>
<load-on-startup>3</load-on-startup>
</servlet>
     
<servlet-mapping id="BPEL_OC4J_Servlet_Mapping_Id">
<servlet-name>BPEL_OC4J_Servlet</servlet-name>
<url-pattern>/*</url-pattern>
</servlet-mapping>
<security-constraint>
     <web-resource-collection>
          <web-resource-name>Default Domain Pages</web-resource-name>
          <description>These pages are only accessible by authenticated users.</description>
          <url-pattern>*orabpel/default/HelloWorld/v2010_05_02__62961</url-pattern>
     </web-resource-collection>
     <auth-constraint>
     <role-name>oc4j-administrators</role-name>
     </auth-constraint>
</security-constraint>
<login-config>
<auth-method>BASIC</auth-method>
<realm-name>jazn.com</realm-name>
</login-config>
<security-role>
<description>BPEL Admins</description>
<role-name>oc4j-administrators</role-name>
</security-role>
<distributable/>
<resource-ref id="ResRef_BPELContainerDataSource_Id">
<res-ref-name>jdbc/BPELServerDataSource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>

<ejb-ref id="EjbRef_CubeFinder_Id">
<ejb-ref-name>ejb/collaxa/system/CubeFinderBean</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.collaxa.cube.engine.ejb.interfaces.ICubeFinderBeanHome</home>
<remote>com.collaxa.cube.engine.ejb.interfaces.ICubeFinderBean</remote>
</ejb-ref>
<ejb-ref id="EjbRef_Dispatcher_Id">
<ejb-ref-name>ejb/collaxa/system/DispatcherBean</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.collaxa.cube.engine.ejb.interfaces.IDispatcherBeanHome</home>
<remote>com.collaxa.cube.engine.ejb.interfaces.IDispatcherBean</remote>
</ejb-ref>
<ejb-local-ref>
<ejb-ref-name>ejb/local/CubeEngineLocalBean</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.collaxa.cube.engine.ejb.interfaces.ICubeEngineLocalBeanHome</local-home>
<local>com.collaxa.cube.engine.ejb.interfaces.ICubeEngineLocalBean</local>
<ejb-link>CubeEngineBean</ejb-link>
</ejb-local-ref>
<ejb-local-ref>
<ejb-ref-name>ejb/local/ProcessManagerLocalBean</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.oracle.bpel.client.ejb.interfaces.IBPELProcessManagerLocalBeanHome</local-home>
<local>com.oracle.bpel.client.ejb.interfaces.IBPELProcessManagerLocalBean</local>
<ejb-link>ProcessManagerBean</ejb-link>
</ejb-local-ref>
<ejb-local-ref>
<ejb-ref-name>ejb/local/CubeDeliveryLocalBean</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.collaxa.cube.engine.ejb.interfaces.ICubeDeliveryLocalBeanHome</local-home>
<local>com.collaxa.cube.engine.ejb.interfaces.ICubeDeliveryLocalBean</local>
<ejb-link>CubeDeliveryBean</ejb-link>
</ejb-local-ref>
<ejb-local-ref>
<ejb-ref-name>ejb/local/KeyGeneratorLocalBean</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.collaxa.cube.engine.ejb.interfaces.IKeyGeneratorLocalBeanHome</local-home>
<local>com.collaxa.cube.engine.ejb.interfaces.IKeyGeneratorLocalBean</local>
<ejb-link>KeyGeneratorBean</ejb-link>
</ejb-local-ref>
<ejb-local-ref>
<ejb-ref-name>ejb/local/MessageLocalBean</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.collaxa.cube.engine.ejb.interfaces.IMessageLocalBeanHome</local-home>
<local>com.collaxa.cube.engine.ejb.interfaces.IMessageLocalBean</local>
<ejb-link>MessageBean</ejb-link>
</ejb-local-ref>
<ejb-local-ref>
<ejb-ref-name>ejb/local/ServerLocalBean</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
     <local-home>com.oracle.bpel.client.ejb.interfaces.IServerLocalBeanHome</local-home>
<local>com.oracle.bpel.client.ejb.interfaces.IServerLocalBean</local>
<ejb-link>ServerBean</ejb-link>
</ejb-local-ref>
</web-app>
jazn.xml : C:\product1\10.1.3.1\OracleAS_1\j2ee\home\config
<?xml version = '1.0' encoding = 'UTF-8' standalone = 'yes'?>
<jazn xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/jazn-10_0.xsd" schema-major-version="10" schema-minor-version="0" provider="XML" location="./system-jazn-data.xml" default-realm="jazn.com" persistence="ALL">
     <property name="custom.sso.url.login" value="/jsso/SSOLogin"/>
     <property name="custom.sso.key.alias" value="{AES-128}dpvTz49oIQWnM1gZfdpZ1w=="/>
     <property name="idm.token.asserter.class" value="oracle.security.jazn.sso.SSOCookieTokenAsserter"/>
     <property name="idm.token.collector.class" value="oracle.security.jazn.sso.SSOCookieTokenCollector"/>
     <property name="idm.token.type" value="HTTP_COOKIE"/>
     <property name="idm.token.collector.cookie.1" value="ORA_OC4J_SSO"/>
     <property name="custom.sso.url.logout" value="/jsso/SSOLogout"/>
     <property name="idm.authentication.name" value="JavaSSO"/>
</jazn>
system-jazn-data.xml
<?xml version="1.0" encoding="UTF-8" standalone='yes'?>
<jazn-data
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/jazn-data-10_0.xsd"
schema-major-version="10"
schema-minor-version="0"
>

<jazn-realm>
     <realm>
          <name>jazn.com</name>
          <users>
               <user>
                    <name>Bharani</name>
                    <guid>99116C7155E211DFBFB59D7811B59628</guid>
                    <credentials>{903}26NFSvxAeBAo3nBkbvJ/e2BCD+actZzi</credentials>
               </user>
          </users>
               <role>
                    <name>oc4j-administrators</name>
                    <display-name>OC4J Admin Role</display-name>
                    <description>Administrative role for OC4J</description>
                    <guid>8A00C8701A0511DFBF99734349FF0592</guid>
                    <members>
                         <member>
                              <type>user</type>
                              <name>oc4jadmin</name>
                         </member>
                    </members>
               </role>
          </roles>
     </realm>
</jazn-realm>

<jacc-repository>
</jacc-repository>
<jazn-policy>
     <grant>
          <grantee>
               <principals>
                    <principal>
                         <realm-name>jazn.com</realm-name>
                         <type>role</type>
                         <class>oracle.security.jazn.spi.xml.XMLRealmRole</class>
                         <name>jazn.com/oc4j-administrators</name>
                    </principal>
               </principals>
          </grantee>
          <permissions>
               <permission>
                    <class>oracle.security.jazn.policy.AdminPermission</class>
                    <name>oracle.security.jazn.realm.RealmPermission$jazn.com$createrole</name>
               </permission>
               <permission>
                    <class>oracle.security.jazn.policy.AdminPermission</class>
                    <name>oracle.security.jazn.realm.RealmPermission$jazn.com$modifyrealmmetadata</name>
               </permission>
               <permission>
                    <class>oracle.security.jazn.policy.AdminPermission</class>
                    <name>oracle.security.jazn.policy.RoleAdminPermission$jazn.com/*$</name>
               </permission>
               <permission>
                    <class>oracle.security.jazn.policy.AdminPermission</class>
                    <name>oracle.security.jazn.realm.RealmPermission$jazn.com$createrealm</name>
               </permission>
               <permission>
                    <class>oracle.security.jazn.policy.AdminPermission</class>
                    <name>oracle.security.jazn.realm.RealmPermission$jazn.com$droprealm</name>
               </permission>
               <permission>
                    <class>oracle.security.jazn.policy.AdminPermission</class>
                    <name>oracle.security.jazn.realm.RealmPermission$jazn.com$droprole</name>
               </permission>
               <permission>
                    <class>oracle.security.jazn.policy.RoleAdminPermission</class>
                    <name>jazn.com/*</name>
               </permission>
               <permission>
                    <class>com.evermind.server.AdministrationPermission</class>
                    <name>administration</name>
                    <actions>administration</actions>
               </permission>
               <permission>
                    <class>oracle.security.jazn.realm.RealmPermission</class>
                    <name>jazn.com</name>
                    <actions>modifyrealmmetadata</actions>
               </permission>
               <permission>
                    <class>oracle.security.jazn.realm.RealmPermission</class>
                    <name>jazn.com</name>
                    <actions>createrealm</actions>
               </permission>
               <permission>
                    <class>oracle.security.jazn.realm.RealmPermission</class>
                    <name>jazn.com</name>
                    <actions>dropuser</actions>
               </permission>
               <permission>
                    <class>oracle.security.jazn.realm.RealmPermission</class>
                    <name>jazn.com</name>
                    <actions>droprealm</actions>
               </permission>
               <permission>
                    <class>com.evermind.server.rmi.RMIPermission</class>
                    <name>login</name>
               </permission>
               <permission>
                    <class>com.evermind.server.rmi.RMIPermission</class>
                    <name>subject.propagation</name>
               </permission>
          </permissions>
     </grant>
     <grant>
          <grantee>
               <principals>
                    <principal>
                         <realm-name>jazn.com</realm-name>
                         <type>role</type>
                         <class>oracle.security.jazn.spi.xml.XMLRealmRole</class>
                         <name>jazn.com/ascontrol_admin</name>
                    </principal>
               </principals>
          </grantee>
          <permissions>
               <permission>
                    <class>oracle.security.jazn.policy.AdminPermission</class>
                    <name>oracle.security.jazn.realm.RealmPermission$jazn.com$createrole</name>
               </permission>
               <permission>
                    <class>oracle.security.jazn.policy.AdminPermission</class>
                    <name>oracle.security.jazn.realm.RealmPermission$jazn.com$modifyrealmmetadata</name>
               </permission>
               <permission>
                    <class>oracle.security.jazn.policy.AdminPermission</class>
                    <name>oracle.security.jazn.policy.RoleAdminPermission$jazn.com/*$</name>
               </permission>
               <permission>
                    <class>oracle.security.jazn.policy.AdminPermission</class>
                    <name>oracle.security.jazn.realm.RealmPermission$jazn.com$createrealm</name>
               </permission>
               <permission>
                    <class>oracle.security.jazn.policy.AdminPermission</class>
                    <name>oracle.security.jazn.realm.RealmPermission$jazn.com$droprealm</name>
               </permission>
               <permission>
                    <class>oracle.security.jazn.policy.AdminPermission</class>
                    <name>oracle.security.jazn.realm.RealmPermission$jazn.com$droprole</name>
               </permission>
               <permission>
                    <class>oracle.security.jazn.policy.RoleAdminPermission</class>
                    <name>jazn.com/*</name>
               </permission>
               <permission>
                    <class>com.evermind.server.AdministrationPermission</class>
                    <name>administration</name>
                    <actions>administration</actions>
               </permission>
               <permission>
                    <class>oracle.security.jazn.realm.RealmPermission</class>
                    <name>jazn.com</name>
                    <actions>modifyrealmmetadata</actions>
               </permission>
               <permission>
                    <class>oracle.security.jazn.realm.RealmPermission</class>
                    <name>jazn.com</name>
                    <actions>createrealm</actions>
               </permission>
               <permission>
                    <class>oracle.security.jazn.realm.RealmPermission</class>
                    <name>jazn.com</name>
                    <actions>dropuser</actions>
               </permission>
               <permission>
                    <class>oracle.security.jazn.realm.RealmPermission</class>
                    <name>jazn.com</name>
                    <actions>droprealm</actions>
               </permission>
               <permission>
                    <class>com.evermind.server.rmi.RMIPermission</class>
                    <name>login</name>
               </permission>
               <permission>
                    <class>com.evermind.server.rmi.RMIPermission</class>
                    <name>subject.propagation</name>
               </permission>
          </permissions>
     </grant>
     <grant>
          <grantee>
               <principals>
                    <principal>
                         <realm-name>jazn.com</realm-name>
                         <type>role</type>
                         <class>oracle.security.jazn.spi.xml.XMLRealmRole</class>
                         <name>jazn.com/oc4j-app-administrators</name>
                    </principal>
               </principals>
          </grantee>
          <permissions>
               <permission>
                    <class>com.evermind.server.rmi.RMIPermission</class>
                    <name>login</name>
               </permission>
          </permissions>
     </grant>
     <grant>
          <grantee>
               <principals>
                    <principal>
                         <realm-name>jazn.com</realm-name>
                         <type>role</type>
                         <class>oracle.security.jazn.spi.xml.XMLRealmRole</class>
                         <name>jazn.com/users</name>
                    </principal>
               </principals>
          </grantee>
          <permissions>
               <permission>
                    <class>com.evermind.server.rmi.RMIPermission</class>
                    <name>login</name>
               </permission>
          </permissions>
     </grant>
     <grant>
          <grantee>
               <principals>
                    <principal>
                         <realm-name>jazn.com</realm-name>
                         <type>user</type>
                         <class>oracle.security.jazn.spi.xml.XMLRealmUser</class>
                         <name>jazn.com/anonymous</name>
                    </principal>
               </principals>
          </grantee>
          <permissions>
               <permission>
                    <class>com.evermind.server.rmi.RMIPermission</class>
                    <name>login</name>
               </permission>
          </permissions>
     </grant>
     <grant>
          <grantee>
               <principals>
                    <principal>
                         <realm-name>jazn.com</realm-name>
                         <type>role</type>
                         <class>oracle.security.jazn.spi.xml.XMLRealmRole</class>
                         <name>jazn.com/BPMSystemAdmin</name>
                    </principal>
               </principals>
          </grantee>
          <permissions>
               <permission>
                    <class>com.collaxa.security.ServerPermission</class>
                    <name>server</name>
                    <actions>all</actions>
               </permission>
          </permissions>
     </grant>
     <grant>
          <grantee>
               <principals>
                    <principal>
                         <realm-name>jazn.com</realm-name>
                         <type>role</type>
                         <class>oracle.security.jazn.spi.xml.XMLRealmRole</class>
                         <name>jazn.com/BPMDefaultDomainAdmin</name>
                    </principal>
               </principals>
          </grantee>
          <permissions>
               <permission>
                    <class>com.collaxa.security.DomainPermission</class>
                    <name>default</name>
                    <actions>all</actions>
               </permission>
          </permissions>
     </grant>
     <grant>
          <grantee>
               <principals>
                    <principal>
                         <realm-name>jazn.com</realm-name>
                         <type>role</type>
                         <class>oracle.security.jazn.spi.xml.XMLRealmRole</class>
                         <name>bpel_users</name>
                    </principal>
               </principals>
          </grantee>
          <permissions>
               <permission>
                    <class>com.evermind.server.AdministrationPermission</class>
                    <name>administration</name>
                    <actions>administration</actions>
               </permission>
               <permission>
                    <class>com.evermind.server.rmi.RMIPermission</class>
                    <name>login</name>
               </permission>
          </permissions>
     </grant>
     <grant>
          <grantee>
               <principals>
                    <principal>
                         <class>sun.security.acl.PrincipalImpl</class>
                         <name>oc4j-administrators</name>
                    </principal>
               </principals>
          </grantee>
          <permissions>
               <permission>
                    <class>java.lang.RuntimePermission</class>
                    <name>setContextClassLoader</name>
               </permission>
          </permissions>
     </grant>
</jazn-policy>

<jazn-loginconfig>
     <application>
          <name>oracle.security.jazn.oc4j.CertificateAuthenticator</name>
          <login-modules>
               <login-module>
                    <class>oracle.security.jazn.login.module.X509LoginModule</class>
                    <control-flag>required</control-flag>
                    <options>
                         <option>
                              <name>addAllRoles</name>
                              <value>true</value>
                         </option>
                    </options>
               </login-module>
          </login-modules>
     </application>
     <application>
          <name>oracle.security.jazn.tools.Admintool</name>
          <login-modules>
               <login-module>
                    <class>oracle.security.jazn.login.module.RealmLoginModule</class>
                    <control-flag>required</control-flag>
                    <options>
                         <option>
                              <name>addAllRoles</name>
                              <value>true</value>
                         </option>
                    </options>
               </login-module>
          </login-modules>
     </application>
     <application>
          <name>oracle.security.jazn.oc4j.WebCoreIDSSOAuthenticator</name>
          <login-modules>
               <login-module>
                    <class>oracle.security.jazn.login.module.coreid.CoreIDLoginModule</class>
                    <control-flag>required</control-flag>
                    <options>
                         <option>
                              <name>coreid.name.attribute</name>
                              <value>your credential mapping variable name</value>
                         </option>
                         <option>
                              <name>addAllRoles</name>
                              <value>true</value>
                         </option>
                         <option>
                              <name>coreid.resource.operation</name>
                              <value>your oreid resource operation</value>
                         </option>
                         <option>
                              <name>coreid.resource.type</name>
                              <value>your coreid resource type</value>
                         </option>
                         <option>
                              <name>coreid.name.header</name>
                              <value>your http header name variable</value>
                         </option>
                         <option>
                              <name>coreid.resource.name</name>
                              <value>your coreid resource name</value>
                         </option>
                         <option>
                              <name>coreid.password.attribute</name>
                              <value>your password authentication variable</value>
                         </option>
                         <option>
                              <name>coreid.password.header</name>
                              <value>your http header password variable</value>
                         </option>
                    </options>
               </login-module>
          </login-modules>
     </application>
     <application>
          <name>oracle.security.wss.jaas.SAMLAuthManager</name>
          <login-modules>
               <login-module>
                    <class>oracle.security.jazn.login.module.saml.SAMLLoginModule</class>
                    <control-flag>required</control-flag>
                    <options>
                         <option>
                              <name>issuer.name.1</name>
                              <value>www.oracle.com</value>
                         </option>
                         <option>
                              <name>addAllRoles</name>
                              <value>true</value>
                         </option>
                    </options>
               </login-module>
          </login-modules>
     </application>
     <application>
          <name>oracle.security.jazn.oc4j.DigestAuthenticator</name>
          <login-modules>
               <login-module>
                    <class>oracle.security.jazn.login.module.digest.DigestLoginModule</class>
                    <control-flag>required</control-flag>
                    <options>
                         <option>
                              <name>addAllRoles</name>
                              <value>true</value>
                         </option>
                    </options>
               </login-module>
          </login-modules>
     </application>
     <application>
          <name>oracle.security.jazn.oc4j.JAZNUserManager</name>
          <login-modules>
               <login-module>
                    <class>oracle.security.jazn.login.module.RealmLoginModule</class>
                    <control-flag>required</control-flag>
                    <options>
                         <option>
                              <name>addAllRoles</name>
                              <value>true</value>
                         </option>
                    </options>
               </login-module>
          </login-modules>
     </application>
     <application>
          <name>oracle.security.wss.jaas.JAASAuthManager</name>
          <login-modules>
               <login-module>
                    <class>oracle.security.jazn.login.module.WSSLoginModule</class>
                    <control-flag>required</control-flag>
                    <options>
                         <option>
                              <name>addAllRoles</name>
                              <value>true</value>
                         </option>
                    </options>
               </login-module>
          </login-modules>
     </application>
</jazn-loginconfig>
<jazn-permission-classes>
</jazn-permission-classes>
</jazn-data>
It is huge to check all these files, but for reference providing all the files for checking the security details.
Thanks for your help...

Missing partitions after running Recovery from previous System Image Backup in Windows 8.1

After running Recovery from a recent Sytem Image Backup the LRS_ESP partition is now missing and the Used space on the PBR_DRV partition is reported as 95.20MB while it previously reported 9.52GB in use. The WINRE_DRV, SYSTEM_DRV, Windows8_OS and D:LENOVO partions appear to be OK.
I ran the Recover after replacing the original 500GB HDD with a 1TB. Any details/links/recommendations on recreating/correcting the LRS_ESP and PBR_DRV partitions? Thanks!

Here are the before and after partition details obtained through Partition Wizard:
Link to image 1
Link to image 2
Moderator note: large image(s) converted to link(s): About Posting Pictures In The Forums

Data recovery from corrupt boot partition

The boot partition on my MacBook running 10.7.6 has a corrupt volume structure and will not mount, much less boot. The recovery partition boots but really doesn't let me do anything. Disk Utility can't repair nor even complete verification. I have lots of images which I need to recover, so am looking for a utility which might help.
Everything was apparently ok until the failure and the drive hardware checked out ok, so I'm hopeful my files are recoverable. A week or so ago I optimized the volume with TechTool Pro and the directory with DiskWarrior, and last night attempted to sync 1Password on my iPad with 1Password for Mac. This did no t work, probably because of my unfamiliarity with the procedure, but seemed to do no damage. When I ran TTPro last night from its eDrive partition it reported a volume structure problem on the partition which I started to fix with the program but then cancelled the analysis and decided to use disk utility instead. Disk utility also reported a problem but stopped the verification with the instruction to do a repair which it again could not complete. When I rebooted the system partition would again not boot but this time I got grey screen with a message that the debugger had loaded and <panic>. A message box said power down and restart, but that only repeats the process.
I'm thinking of attempting to install a system on an external boot drive and accessing the corrupt partition with a data recovery utility. Any insights, ideas or shared experiences appreciated. Thanks in advance for any desperately needed help.

The safest thing to do here is to install a new disk in the system and do a clean install of OS X. From there, you can put your corrupted volume in an external USB enclosure and mount the file system to try and recover as much data as you can.
It's likely obvious now, but it's REALLY worth investing in a large-capacity external storage or Time Capsure to use with Time Machine. Backups are essential. Hardware always eventually dies. We all need an effective strategy to deal with that.
A long time ago, I was backing my Linux system up to 4mm DAT. When the inevitable HDD crash came, I thought I was ready. Unfortunately, I hadn't tested recovery from tape and I ended up losing everything. Which is to say, until you know you can restore, you don't even have a backup. I lost thousands upon thousands of photos of my kids growing up.
BTW, if it is essential that you recover as much as possible, consider taking the disk to a data recovery service. Be warned: It's expensive.

Directlink to BPEL Engine - Recovery from EM

Similar Messages

Maybe you are looking for