Not able to start AdminServer,Caused By: oracle.security.jps.JpsRuntimeException: JPS-00056: Failed to create identity store service instance idstore.ldap.provider:idstore.ldap. Reason: oracle.security.jps.JpsRuntimeException: JPS-00027: internal error You configured a generic WLS LDAPAuthenticator. The identity store type cannot be determined. Please choose an LDAP Authentication provider that matches your LDAP server.

Issue 

Not able to start AdminServer due to 

Caused By: oracle.security.jps.JpsRuntimeException: JPS-00056: Failed to create identity store service instance idstore.ldap.provider:idstore.ldap. Reason: oracle.security.jps.JpsRuntimeException: JPS-00027: internal error You configured a generic WLS LDAPAuthenticator.
The identity store type cannot be determined. Please choose an LDAP Authentication provider that matches your LDAP server.

####<Feb 3, 2015 12:51:27 PM CST> <Critical> <WebLogicServer> <localhost> <adminserver> <Main Thread> <<WLS Kernel>> <> <> <1422989487383> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-00056: Failed to create identity store service instance idstore.ldap.provider:idstore.ldap. Reason: oracle.security.jps.JpsRuntimeException: JPS-00027: internal error You configured a generic WLS LDAPAuthenticator.
The identity store type cannot be determined. Please choose an LDAP Authentication provider that matches your LDAP server.
weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-00056: Failed to create identity store service instance idstore.ldap.provider:idstore.ldap. Reason: oracle.security.jps.JpsRuntimeException: JPS-00027: internal error You configured a generic WLS LDAPAuthenticator.
The identity store type cannot be determined. Please choose an LDAP Authentication provider that matches your LDAP server.
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1402)
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1022)
        at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
        at weblogic.security.SecurityService.start(SecurityService.java:141)
        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: oracle.security.jps.JpsRuntimeException: JPS-00056: Failed to create identity store service instance idstore.ldap.provider:idstore.ldap. Reason: oracle.security.jps.JpsRuntimeException: JPS-00027: internal error You configured a generic WLS LDAPAuthenticator.
The identity store type cannot be determined. Please choose an LDAP Authentication provider that matches your LDAP server.

        at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:170)



Solution: 

Please chekc the config.xml file and change the 

<sec:authentication-provider xsi:type="wls:ldap-authenticatorType">
        <sec:name>AD_Authenticator_1</sec:name>

to 

<sec:authentication-provider xsi:type="wls:active-directory-authenticatorType">
        <sec:name>AD_Authenticator_1</sec:name>

Weblogic Full RoadMap

The Server Lifecycle

SHUTDOWN. In this state, the server is configured but inactive. 

STARTING. When you start a server, it takes the following actions:Retrieves its configuration data.  

STANDBY. (Available only if you have configured an administration port.) You can issue a command that starts a server and places it in this state. In this state, a server has initialized all of its services and applications and can accept administration commands and participate in cluster communication. It is not accessible for requests that come from external clients.

A typical use of the STANDBY state is to keep a server available as a "hot" backup, especially in a high-availability or mission-critical environment. When you need to use the backup server, you can quickly resume its ability to process client requests. 

RUNNING. In this state, a server offers its services to clients and can operate as a full member of a cluster

SHUTDOWN. You can move a server into this state either from the RUNNING state or the STANDBY state. As it transitions to SHUTDOWN, a server goes through the SHUTTING_DOWN state

FAILED. If one or more critical services become dysfunctional during the lifetime of server, the server transitions to the FAILED state. Your only option to recover from the FAILED state is to shut down the server. You can set up a server to restart itself if critical services become dysfunctional. For information about automatic restarts, Guide. 

UNKNOWN. If a server cannot be contacted, it is considered to be in the UNKNOWN state.

WebLogic 12c & SOA 12c

The road ahead for WebLogic 12c

Before we can describe all the new features of WebLogic 12.1.3 & 12.1.4 and compare this to the 12.1.2 version we should first take a look at the 10.3.6 version. WebLogic 10.3.6 is still the latest 11g version but Oracle will support 10.3.6 till 2018 and extended support till 2021. So Oracle’s Fusion Apps and we have enough time to migrate to WebLogic 12.1.X. Oracle also promised that the upgrade should be easy.  That being said we can take look at the WebLogic 12.1.X features.

Last summer Oracle already released WebLogic 12.1.2 which has since WebLogic 12.1.1 been certified for Java EE 6 and it looks like the Java EE 7 certification is still far away, so Oracle updated the 12.1.2 version with some badly needed frameworks like WebSockets. To make the developer experience more complete Oracle added more support for Maven and it comes with a utility to synchronize a Maven repository with all the needed WebLogic libraries.

12.1.2 is also the first release, which comes with Fusion Middleware infrastructure components. For now FMW 12.1.2 contains ADF & OWSM and comes with Enterprise Manager & MDS.
WebLogic 12.1.2 replaced the BEA installer and the BSU patching utilities with the Oracle Universal Installer and the OPatch utilities for applying patches.  To make it even more easier it just comes in one taste ( no Java included or a specific Operating System installer ).  Just one big jar file for WebLogic with Coherence or one for WebLogic, Coherence and FMW.

WebLogic 12.1.2 introduced Dynamic Clusters, Elastic JMS and integrated Coherence configuration and management. Dynamic Clusters is a great feature to extend the WebLogic Cluster with Managed Servers based on a Server Template. For this we only need to change a parameter on the cluster and the new Managed Servers are distributed over the NodeManagers. To use this feature your blades need to have enough free resources to handle the extra Managed Servers.
Elastic JMS can be combined with Dynamic Clusters, this way we only need to create 1 JMS server, target this to the cluster and every Cluster node will have its own JMS server.

When we look at the announced features of WebLogic 12.1.3 and 12.1.4 we can see that Oracle continues on this road.

WebLogic 12.1.3 will be the first version for many FMW 12c products like Oracle SOA Suite 12c and probably come in one big jar. 12.1.3 & 12.1.4 will add extra features and improvements to Elastic JMS & Dynamic Clusters. Elastic JMS in 12.1.3 will support Server Migration so you can’t lose any JMS messages.
In 12.1.4, Dynamic Clusters will have support for auto-scaling based on thresholds based on user-defined metrics. WebLogic 12.1.4 will also have an API to control the Dynamic Clusters, this way we can easily program when to stop, start or remove nodes from a dynamic cluster.

WebLogic 12.1.3 will come with the JDBC 12c driver, this driver will gives us better integration and reliability between WebLogic 12c and Oracle Database 12c (Application Continuity).
When we take a look at the administration side of WebLogic we can see that the Enterprise Manager will be more important, in WebLogic 12.1.3 we can also do Application and JMS administration from the EM application. Also 12.1.3 will contain a Restful management APIs for additional monitoring, operations, Datasource and deployment support.  Plus a global OWSM policy to protect all your Web and Rest services with one server policy.

WebLogic 12.1.4 will have a new feature called Multi-Tenant Applications, this way you can define an WebLogic template for an application, so one or more customers of this application which will have its own Cluster, Managed Servers, Application and (not shared) resources plus it will support Oracle Database 12c pluggable databases.



The last part of this article will talk about the development side of WebLogic 12.1.3 and 12.1.4.  First WebLogic 12.1.3 has to be the Modern Development Platform and will focus on HTML5 development.

12.1.3 has some great new features like
• Updated version of JAX-RS and WebSockets.
• Server-Sent Events, this allows you to continuously sending updates to the browsers.
• JSON-P or JSON with Padding will solve your cross domain security problems.
• Maven improvements.
• Avatar allows you to develop and deploy server side Javascript Services without knowing Java.

WebLogic 12.1.4 will be certified for Java EE 7 and this means the WebLogic platform will get some framework updates and some new frameworks like
• Java API for JSON 1.0
• Java API for WebSocket 1.0
• Batch Applications 1.0
• Concurrency Utilities 1.0


The last question is off course when can we expect WebLogic 12.1.3 & 12.1.4.  The 12.1.3 version will probably be released in March or April and 12.1.4 will be much later.

Weblogic Domain Creation



Weblogic Domain Creation:

Platform Installation of the Oracle Weblogic 10.3.6.0 completed.

Next we are going to create new Domain in Oracle weblogic.

The following domain creation particularly in Windows

 Step 1 

 Determine the appropriate domain creation mode for your situation. The domain creations are in below modes:  

                    

Graphical mode, console mode, silent mode.

At present we are going to see Graphical Mode installation.

Step 2

Navigate to path Local drive (E:) \ Oracle \ Middleware \ wlserver_10.3 \ Common \ bin

Step 3 

Double click on the Config.cmd file.

Step 4

Welcome window display to create a new weblogic domain and click next.

Step 5

Select Domain source window displays automatically generate a domain configuration and Click Next.

Step 6

Domain Name and Location windows displays.

Make the domain name as you like Eg : Sample_Domain, Test_Domain .

Default Location for the doamin creation is Local Drive (E:) \Oracle \ Middleware \ user_projects \ domain.

Click Next.

Step 7

Configure Administrator user Name and Password window displays.

Name: weblogic

Password: “As you like” eg : welcome1

Confirmation password: welcome1

Click Next.

Step 8

Configure Server start Mode and Jdk window display.

We need to select either Development mode or Production mode and click next.

Development mode:

The default JDK for development domain is Sun Hotspot
You can use the demo certificates for SSL
Auto deployment is enabled
Server instances rotate their log files on startup
Admin Server uses an automatically created boot.properties during startup
The default maximum capacity for JDBC Datasource is 15

Production mode:

The default JDK for production domain is JRockit
If you use the demo certificates for SSL a warning is displayed
Auto deployment is disabled
Server instances rotate their log files when it reaches 5MB
Admin Server prompts for username and password during startup
The default maximum capacity for JDBC Datasource is 25

Step 9

We can create Administration sever, Managed server, Cluster and Machine simultaneously, while creating domain.

Mark tick in the check box. Click next.

Step 10

Creation of Administration server.

Default port for Admin server is 7001, we can also change the Listen port.  Click Next

Step 11

Creation of Managed server.

Server Name: ms1

Needs to change the Listen port as 7003 and each managed server have unique Listen port and click next

Step 12 

Creation of Machine.

Machine Name : m1

Default Node manager Listen port is 5556. Click next

Step 13

Assigning managed servers to Machine.

So in this step managed server(ms1) is under machine(m1).

Click next.

Step 14

New domain creation structure and click create.

Step 15

New Domain creation is in progress. After reached 100% mark the check box [start Admin server]

The admin server will start. Finally click done. 

Domain has been created successfully.

Weblogic Console Admin URL : http://localhost:7001/console