www.phurnace.com At the WebSphere Portal Excellence Conference, Phurnace Software will announce the release of Phurnace Portal Deliver which will allow Sys Admins to roll back deployments of WebSphere Portal to a previous known good state. Phurnace builds software to help companies automate the deployment of J2EE applications and configuration of WebSphere, WebLogic, JBoss or WebSphere Portal. Phurnace Software helps you accelerate your delivery of production-ready Java EE™ applications. Our flagship product, Phurnace Deliver™, all but eliminates configuration-related errors, and dramatically reduces your dependency on scripting.
Data Recovery Software Download Software Internet Security System Discovery Card
IT infrastructure Library (ITIL) has been around since 1989. Since v2 was released at the beginning of the millennium, there has been a shift in the perspective with which IT is viewed. Adopting ITIL 2 has cut the total cost of ownership (TCO) for billion dollar corporations by up to 48% according to internet.com.
While ITIL 2 has helped organizations who have implemented it apply the principles of process change management to their IT operations, it still stops short in providing guidance on how to integrate IT functions into the business. This has made it easy for management to overlook the very real benefits contributed to the business by IT.
ITIL 3 helps resolves this issue. Rather than focusing on process, ITIL 3 focuses on service. It’s designed to incorporate the best practices of change management. A side benefit is that ITIL problem management process flow also becomes much more business centered in its scope.
The challenge many businesses face as they seek to implement ITIL 3 is how to approach IT problem management. What tools provide the 360 situational awareness necessary to implement this important process in ITIL 3? What products in the market deliver on the promise to facilitate the move towards ITIL and service oriented IT management strategies?
Business Transaction Monitoring
Gartner in the 2010 APM Magic Quadrant report and Forrester Research in its Competitive Analysis: Application Performance Management and Business Transaction Monitoring report have both identified these two technologies as key components of developing a service focused technology approach to business needs as contrasted to a function-based approach.
To borrow a term from design-form has roughly followed function. The form has struggled to provide dependable service. For too many years, form has preceded function. Multiple functional pieces (applications) have been developed in separate silos each dealing with its own business process. Each of these applications are supposed to be serving the business yet the design of the system, if form, makes consistent service impossible without outside help.
Problem management in a world of silos is very ineffective. This why business transaction monitoring is an important component for implementing either ITIL 2 or ITIL 3. It helps in the successful implementation of ITIL Problem Management as it enables the reconfiguring of IT operation structure from one where individual silos operate independently of each other, to one where many disparate processes and tools work interdependently.
Before the advent of business transaction monitoring (BTM), IT departments were so busy trying to discover where problems were occurring and then patching the problems up that providing dependable service was a nightmare. Business transaction monitoring changes this. BTM makes it possible to track a business transaction through its path of execution-which may include many Java,.NET, messaging middleware, CICS and database applications. Each IT transaction that comprises the business transaction must execute correctly and complete within the time allocated by the service level agreement (SLA).
BTM provides deep visibility into the application stack, enabling IT operations to readily see how a small IT issue can cause a large business impact. Testing application performance in QA can assess service impacts before new releases are deployed into production. It also provides the essential visibility to detect potential problems in transaction flow long before they have a chance to cascade into problems that impact customers.
Application Performance Management
Application performance management (APM) incorporates BTM but can do more. The right APM solution should employ an embrace-until-you-can-replace design. This means that an APM with a library of technology solutions designed to work with the leading IT technology lines: IBM WebSphere MQ, IBM WebSphere ESB, IBM WAS, IBM WBI, J2EE, TIBCO EMS, TIBCO RV, BEA WebLogic, Oracle Database, SQL Server, JMX, JBoss, and WMQ SPI for HP Operations Center, etc. will enable the implementation of ITIL all that easier.
Complex Event Processing
An application performance management solution must also have the ability to handle huge volumes of diverse data. In order to do this effectively, a complex event processing (CEP) engine needs to filter, correlate, contextualize, and analyze data captured from disparate live data sources (RSS feeds, internal IT technology, cloud-based technology, etc.). Then the CEP needs to respond to the information automatically with warning alerts and possibly automated repairs.
Introduction
Oracle WebLogic Server 10.3 came up with lots of advancements and features to make this application server f a better choice for building and deploying and services of. It supports Rich Internet Application (RIA) via the new server-side HTTP publish-subscribe engine. Oracle attempts to make this version compatible with previous versions of WebLogic Server in the areas of persistent data, generated classes, and API compatibility.
JDK 1.4 Vs JDK 1.6
As you will be upgrading code from JDK 1.4 to 1.6, some of the important features which were not present in JDK 1.4 are Generics
Generics is a feature added in the JDK1.5 for adding compile-time type safety to the Collections Framework.While taking an element out of a Collection, you must cast it to the type of element that is stored in the collection. This is unsafe as well as inconvenient also. This casting can fail at run time as compiler does not check whether your cast is same as collection type or not.
You have to communicate the type of a collection to the compiler to avoid above situation. Generics provide a way for you to communicate the type of a collection to the compiler, so that it can be checked. Once the compiler knows the element type of the collection, the compiler can check that you have used the collection consistently and can insert the correct casts on values being taken out of the collection.
Enhanced for Loop
This newly added feature eliminates the use of iterators and index variables when iterating over collections and arrays.
Autoboxing/Unboxing
Autoboxing is basically automatic conversion of primitive types to their equivalents. Like automatic conversion of (int, float, double etc.) to (Integer, Float, Double,…).
The reverse process of autoboxing is called Unboxing. Unboxing is automatic conversion of wrapper types to their primitive equivalents for assignments or method or constructor invocations.
Typesafe Enums
This flexible object-oriented enumerated type facility allows you to create enumerated types with arbitrary methods and fields. It provides all the benefits of the Typesafe Enum pattern.
Varargs
This facility eliminates the need for manually boxing up argument lists into an array when invoking methods that accept variable-length argument lists.
JDBC Changes
As of WebLogic Server 9.0 and 10.x, the number of JDBC resource types was reduced to simplify JDBC configuration. Now, instead of configuring a JDBC connection pool and then configuring a data source a source to point to the connection pool and bind to the JNDI tree, you can configure a data source that encompasses a connection pool.
Configuring JDBC
In the Domain Structure tree, expand Services > JDBC, then select Data Sources.
Click on New to create a new data Source.
Enter Name, JNDI Name for data source.
Database Type:-Select the DBMS of the database that you want to connect to. If your DBMS is not listed, select Other.
Database Driver:-The list will show common drivers for selected DBMS. Select the driver you want to use to connect to database.
Here we have selected Non-XA driver so, we need to select transaction options which will be next screen. If we select XA-driver transaction options will be default(The data source will support global transactions and use the ‘Two-Phase Commit’ global transaction protocol).
Click next to continue
Select Transaction options on the above screen. All the options are self explanatory; select them according to your application needs.
Click Next to continue
Now you have to create a connection pool
Enter Database Name, Host Name, Port No Database User Name and Password in the above screen and click next to continue
A Test connection screen will open showing the connection details. You can test the configuration by Clicking Test configuration or just click Finish.
JDBC Feature Changes
The following section describes some of the important changes to JDBC support:
JDBC 4.0 Support
WebLogic Server 10.3 supports JDBC 4.0 specification. The WebLogic Type 4 JDBC driver for Oracle has been deprecated in WebLogic Server 10.3 and might be removed in next release. So I would suggest instead of using deprecated driver, you should use the Oracle Thin Driver that comes with WebLogic Server.
Oracle 11g RAC Support
WebLogic Server 10.3 includes support for Oracle 11g and 11g RAC (Real Application Clusters)
JMS configuration changes
Go to Domain, Services, Messaging, JMS Modules.
JMS configurations in this release of weblogic server are a bit different or you can say a bit interesting than WLS8.1. Here you will create a JMS module which contains all the things you are used to working with in 8.1. All the JMS Connection Factories, JMS Queues, distributed destinations, topics etc will go in a JMS module. This gives you the advantage of flexibility while targeting the resources. It also allows you to define application specific JMS modules and only deploy them when the application is deployed.
So, create a JMS module, assign it a name such as MyJMSModule. Now Select targeting options, then add resources to the module. This is where you add the connection factories, queues, topics, distributed destinations and so on.
In the Administration Console, expand Services > Messaging and select JMS Modules
Click New to create a Module. A module named SystemModule is shown here. Don’t get confused with the name System module it’s not default module, its created for our application.
Name:- Enter any name for the JMS module.
Descriptor file Name: optionally enter a name for module’s underlying descriptor file. The system will automatically add a “-jms.xml” extension to this name. If you do not provide a name, a default name will be assigned.
Location in Domain: optionally, enter where you want to place the descriptor for the system module. The location must be relative to JMS configuration subdirectory of your domain, which is the config/jms subdirectory.
Click on Next to continue
Select the server on to deploy module.
Click Next to continue.
On the above page, indicate whether you want to be able to immediately add resources to this JMS Module after it’s created.
Click Finish.
If you chose not to continue adding resources, the JMS module creation is complete, and you are taken to the JMS Modules summary page where you can access the new module to edit it and add resources to it. However, if you chose to continue adding resources, then you are automatically taken to the JMS Modules: Configuration page where you can continue adding resources to the module.
Click New to add resources.
Select one of the resources which you want to add.
Depending on the type of resource you select, you will be asked to enter information to create the resource same as you do in previous versions.
Uniform Configuration of Distributed Destinations
Uniform Distributed Destination is an interesting feature for applications using distributed destinations in weblogic Server 9.X and later versions. It helps in simplifying the management and development of distributed applications. Now administrator doesn’t need to create or designate destination members, but relies on the system to uniformly create the necessary members on the JMS servers to which a JMS module is targeted. This feature ensures the consistent configuration of all distributed destination parameters. The Weighted Distributed Destination feature is also there for manual fine-tuning of distributed destination members.
While creating distributed queue Leave the Allocate Members Uniformly check box enabled in order for WebLogic Server to uniformly create and allocate the members of this uniform distributed queue.
JSP Compiler
As you might know the in WLS 8.1 JSP compiler uses the javelin to generate byte code. But in this release Java Compiler API’s is used. This feature should not impact JSP files in existing applications. But this is definitely a reliable JSP complier as it doesn’t depend on the Javelin framework Java class bytecode generation feature.
Deployment Descriptors
The weblogic.xml deployment descriptor is now schema-based rather than document type definition (DTD)-based. You can refer http://edocs.bea.com/wls/docs90/webapp/weblogic_xml.html link for complete reference of the elements in the WebLogic Server-specific deployment descriptor weblogic.xml. You can also refer http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd to see the schema for web.xml.
Upgrading Deployment Descriptors
As this weblogic server uses schema-based rather than document type definition (DTD)-based descriptors. So to get full advantage I would suggest upgrading deployment descriptors while migrating application to a new release. A simple tool can be used to get the descriptors upgraded. This tool is known as weblogic.DDConverter.
I would recommend you to put all the generated descriptors in a temporary directory. Inspect the correctness and if they seem fine place them in proper place.
weblogic.DDConverter can be invoked with the following command:
java weblogic.DDConverter [options] archive_file_or_directory
where archive_file_or_directory refers to the EAR, WAR, JAR, or RAR of your application.
The following example shows how to use the weblogic.DDConverter command to generate upgraded deployment descriptors for the test.ear Enterprise application into the subdirectory temp in the current directory:
java weblogic.DDConverter -d temp test.ear
if you get “Exception in thread “main” java.lang.NoClassDefFoundError: weblogic/DDConverter” exception just specify the complete for DDConverter class. Following example is shown using full path.
java -cp D:\bea\wlserver_10.3\server\lib\weblogic.jar; weblogic.DDConverter -d temp test.ear
DDConverter is a class inside weblogic.jar, so specify the path of weblogic.jar.
-d specifies the directory for placing generated descriptors files.
So, you have been out on the Internet and hear people talking about blogs. Weblogs (Blogs for short) are web-based publications consisting of information of all sorts. Some people have personal blogs. Others are using blogs to market a product or service. I use one of my blog as a complimentary informational site to my home based business. It allows me to easily and quickly publish information about my home-based business. It is also a portal for my team to keep abreast of business related information.
What do the word meant "blog"? => Go .. BLOG mean in balinese?
In the Balinese language "blog" is very popular for people unhappy or stupid. Oooh yeahh?
For the Balinese "blog" means "stupid or incompetent (the situation)
so important, "Go blog or blog Sajan" "stupid," "bad luck"
If someone is doing something wrong or mistakes of other people said: "Go to your blog or blog Sajan" is not goneBlog words are not words, but the blog is going formal words are common words needed.
Example:
1. Stupid meaning:
There are two people who write articles. Mr. Wayan write a page and mr. Agung page Writing 2 Suddenly, Mr. Agung write the wrong sentence and mr. Wayan is said: "Blog Sajan Awake (s)"
2.Unlucky meaning:
Mr.wayan mr.agung observe and tanneries. Suddenly the MC said, "the red pen on the bag to come here and havespecial present .. ". Mr.agung says Mr. Wayan; bring the red pen yan .. Wayan said no and Mr. Agung is said to" blog "..
Ha .. haa.haa -:)! I'm not going, but I like to blog in English Blog
See all my weblog article in the Diary.
siravich