Oracle Fusion MiddleWare Administrators School

SOA Admin - SOA Errors or Exceptions

2017-12-19T12:27:00.001+05:30

Infrastructure error—StackOverflowError

StackOverflowError is usually an indication of an infrastructure error, as the error does not appear tied to any specific composite. Based on the logger oracle.soa.bpel.engine.dispatch, it is thrown by the BPEL dispatch engine:

javax.ejb.EJBException: EJB Exception: java.lang.StackOverflowError

Composite instance error—SOAPFaultException

There may be a large number of instances in the infrastructure that receive processing faults from external systems they are interacting with. Here, the Mediator Service Engine (as shown by the oracle.soa.mediator.serviceEngine logger) appears to have thrown a SOAPFaultException, which in itself is not very useful. However, the details of the error are quite clear. This is a business exception thrown by some external service or resource. Though there is no information here to tie it back to a specific composite or instance, the same error, in more detail, can be found in the soa_server1.log file, which will provide you with that information. Rest assured, this exception will also appear in the composite instance fault on the console:

Infrastructure error—DeploymentException

Some infrastructure exceptions are related to the backend components not being available or configured properly. Some of them may be categorized by a warning and not an error, but this is still a problem. Note the following error that appears to be related to a WebLogic JMS Server. In this case, the JMS Server named CustomJMSServer is referencing a persistent file store CustomFileStore that does not exist:

Composite instance error— FabricInvocationException

FabricInvocationException is the most generic error reported by the Oracle SOA Suite 11g SOA Infrastructure. This could be caused by invalid SOAP requests, WS-Addressing issues, or even due to non-accessible endpoints. The following FabricInvocationException error provides a little information about its probable cause. Furthermore the Unable to access the following endpoint(s) explanation is also inadequate and in most cases could be misleading, as it may be related to any number of exceptions.

Infrastructure error—Unable to allocate additional threads

This Unable to allocate additional threads error appears to be quite serious, but it really is not. This is clearly an infrastructure related issue though:

Infrastructure or composite instance error— MDSException

The following exception is due to the fact that at runtime an XSD that was being referred from the MDS was not available:

java.io.IOException: oracle.mds.exception.MDSException: MDS-00054: The file to be loaded oramds:/apps/Fault/Common/XSD/SalesOrderHeader.xsd does not exist.

Infrastructure error—BeanInstantiationException

By now you must know that the engine that is responsible to execute composite instances in your infrastructure is soa-infra, which in itself is a J2EE application. The soa-infra application, in some cases, may fail to load in all the managed servers across a cluster and is partially available due to the following exception:

Instantiation of bean failed; nested exception is org. springframework.beans.BeanInstantiationException: Could not instantiate bean class [oracle.integration.platform.blocks.cluster. CoherenceClusterInterfaceImpl]: Constructor threw exception; nested exception is com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster

Infrastructure error—Unable to extend LOB segment

Not all errors are directly due to issues within your SOA infrastructure. All running and completed instances in Oracle SOA Suite 11g are saved in a backend datastore. Lack of free space in the database may prevent the composite instances from completing their processing. For instance, you are most likely to see the following exception if your database runs out of disk space:

oracle.toplink.exceptions.DatabaseException

Internal Exception: java.sql.BatchUpdateException: ORA-01691: unable to extend lob segment DEV_SOAINFRA.SYS_LOB$$ by 128 in tablespace DEV_ SOAINFRA

WebLogic 12C

2016-02-10T02:03:00.003+05:30

SSL Configuration for Apache

2013-07-05T00:50:00.001+05:30

First make sure that apache installations and SSL changes have done, now use these below steps to configure SSL certificates.

Step 1 : Move to "extra" directory of apache.

Ex: cd /APACHE_HOME/conf/extra

Step 2: Generate Private Key on the Server Running Apache + mod_ssl

Ex: openssl genrsa -des3 -out .key 4096
So your result will be : .key

Step 3: Generate a Certificate Signing Request (CSR)

Ex: openssl req -new -key .key –out .csr
So your result will be : .csr

Step 4: Generate a Self-Signed SSL Certificate

Ex: openssl x509 -req -days 365 -in .csr –signkey .key -out .crt
So your result will be : .crt

Step 5: Generate a CA file

Ex: openssl req -new -x509 -days 365 -key in .key -out in .ca
So your result will be : .ca

Step 6: Generate a DER file

Ex: openssl x509 -in .crt -out .der.crt -outform DER
So your result will be : .der.crt

Step 7: Removal of Passphrase (Optional if you want to remove passphrase)

Ex: openssl rsa -in .key -out new.key
So your result will be : new.key
Now copy that “new.key” to “.key”
Ex : cp new.key .key .

Step 8: Finally copy .key and .crt to /APACHE_HOME/conf/, so use

Ex : cp .key /APACHE_HOME/conf/
cp .crt /APACHE_HOME/conf/

Note : You can change the key capacity to higher or lower (i have given 4096==4 MB) and also key validity to more days (i have given 365==1 Year).

Now you are done with your SSL certificates.

OIAM 11g - Introduction to Oracle Identity and Access Management 11g

2013-05-26T02:29:00.000+05:30

Introduction to Oracle Identity and Access Management 11g

As part of Oracle Fusion Middleware, Oracle Identity Management provides a unified, integrated security platform designed to manage user identities, provision resources to users, secure access to corporate resources, enable trusted online business partnerships, and support governance and compliance across the enterprise.

Oracle Identity Management ensures the integrity of large application grids by enabling new levels of security and completeness to address the protection of enterprise resources and the management of the processes acting on those resources.

Oracle Identity Management provides enhanced efficiency through a higher level of integration, consolidation, and automation, and increased effectiveness in terms of application-centric security, risk management, and governance. Oracle Identity Management supports the full life cycle of enterprise applications, from development to deployment to full-blown production.

Oracle Identity Management Overview:

In just a few years Oracle has established itself as the foremost identity and access management (IAM) vendor by providing an integrated, application-centric product portfolio unmatched by its competitors. Oracle’s ability to anticipate and meet customer demand through a savvy combination of key acquisitions and organic growth has turned the company’s identity and access management offering into the IAM market leader.

Oracle Identity Management Business Benefits:

Oracle Identity Management allows enterprises to manage the end-to-end life cycle of user identities across enterprise resources both within and beyond the firewall, independently from enterprise applications. In other words, Oracle Identity Management’s application-centric approach allows customers to clearly separate business logic from security and resource management, thus promoting development agility and lowering maintenance costs.

Oracle’s strategy for IAM provides the following key benefits:

Complete: Oracle Identity Management provides a comprehensive set of market-leading services including identity administration and role management; user provisioning and compliance; web applications and web services access control; single sign-on and federated identities; fraud detection; strong, multifactor authentication and risk management; role governance and identity analytics, audit and reports.

Integrated: Oracle Identity Management components can be deployed separately or together as an integrated suite of identity services. The various components making up Oracle Identity Management are designed to work together to satisfy each identity management and access control requirement met throughout a business transaction.

Hot-Pluggable: Oracle Identity Management’s standards-based suite of products is designed to support heterogeneous, multiple-vendor development and runtime environments, including operating systems, web servers, application servers, directory servers, and database management systems.

Best-Of-Breed: In addition to Oracle Identity Management’s level of completeness, integration, and hot-pluggability, the components of the suite deliver functional depth and sophistication that, taken individually, makes them market-leading, best-of-breed products.

SOA 11g - Configure Sending Email Notifications

2013-05-24T15:55:00.000+05:30

One of the ways of the SOA Suite 11g for communicating with the outside world – apart of course from web service calls and interaction via technology adapters – is through the new User Messaging Service (UMS), a facility installed in the SOA Domain during installation of the SOA Suite. The UMS enables two-way communication between users (real people) and deployed applications. The communication can be via various channels, including Email, Instant Messaging (IM or Chat), SMS and Voice. UMS is used from several components in Fusion Middleware, for example BPEL, Human Workflow, BAM and WebCenter and can also be used from custom developed applications.

Prerequisites:

Before you can apply this article, you need to have installed the SOA Suite 11g, configured the SOA Domain and have the AdminServer and the SOA Server running. You also need access to the Oracle Enterprise Manager Fusion Middleware Control Console.

Step 1: Configure the UMS Email Driver

The User Messaging Service comes with a number of drivers that each handle traffic for a specific channel. One of the drivers controls the email channel. This driver needs to be configured with the properties of the Mail Server and the email account from which emails are sent.

Go to the Oracle Enterprise Manager Fusion Middleware Control Console (typically http://hostname:7001/em) and open the User Messaging Service node. From the drop down menu in the right hand pane, select the option Email Driver Properties:

The properties that need to be configured for sending emails are indicated in the red rectangle. They are:

· OutgoingMailServer – (Get in touch with the messaging team in your organization)

· OutgoingMailServerPort – (Get in touch with the messaging team in your organization)

· OutgoingMailServerSecurity – (Get in touch with the messaging team in your organization)

· OutgoingDefaultFromAddress – (put anything you like.)

· OutgoingUsername – (Get in touch with the messaging team in your organization)

· OutgoingPassword – (Get in touch with the messaging team in your organization)

Press Apply.

Step 2: Configure the SOA Suite Workflow Notification properties

To make sure that (email) notifications are really sent to the email server, we also need to adjust a setting for the SOA Suite Workflow Notification. Navigate to the properties form via the dropdown menu for SOA Infrastructure, under SOA Administration:

The Workflow Notification Properties are shown. Only one is really important at this point: the Notification Mode (default value is None) must be set to either All or Email, otherwise any notification is not really sent onwards by the SOA Suite to UMS!

Click on Apply

Now restart the SOA Managed Server. If you don’t restart the managed server the email notification doesn’t work!

SOA 11g - SOA Data Base Schema Purging

2012-10-19T12:18:00.001+05:30

This post is about how to control the SOA database schema and its growth while running SOA Suite 11g. All the instructions given here are specifically for SOA Suite 11g version 11.1.1.4. From this version onward there are new scripts provided by Oracle and only updated scripts should be used as this version has schema and table structure changes.

Purging composites instances in Oracle SOA SUITE 11g

There are several ways to purge large amounts of instances in SOA Suite 11g database - dehydration storage;

By dropping the SOA Suite repository and next, to recreate it using RCU creation utility providing exactly the same credentials.
Using Enterprise Manager console; Delete with options
Deleting large number of instances using purge script

Dropping the SOA Suite repository Using RCU: Dropping the SOA Suite repository using RCU is straight forward. Just run the RCU utility select "Drop" instead of "Create" and follow the installer.

Using Enterprise Manager Console: Here, first option, using Enterprise Manager console is ok for small amount of instances where you want to remove one or two thousand instances. For large number of instances it will throw Time out error. There is a option provided in EM console for increasing the timeout period but still its not enough for large amount of data.

Deleting Large Number Of Instances Using Purge Script: This is very useful and straight forward process to clean up SOA database schema. In real world , server are receiving millions of requests in a day and keeping these all data as instances in SOA Suite database schema is very costly. It can affect a performance of the server up to some extent. After few days or month probably you will start receiving table space errors as allotted all the table space is already been used by the instances created within SOA database schema. For this reason you need to plan your tablesapce accordingly and generally it should be in between 50 GB - 80 GB in loaded server. And still it requires regular purging for data on the SOA database.

Below is the process for purging / deleting the composite instances from SOA Database schema.

1. First of all you will required Repository creation utility for 11.1.1.4. This installable contain the all required purging script provided by oracle to purge the database schema. You can find the purge script at location. RCU_HOME/rcu/integration/soainfra/sql/soa_purge.

Note : this script cannot run with Microsoft SQL Server and IBM DB2 Database.

2. In SQL*Plus, connect to the database AS SYSDBA:

3. Execute the following SQL commands:GRANT EXECUTE ON DBMS_LOCK to dev_soainfra;
GRANT CREATE ANY JOB TO dev_soainfra;

4. RCU_HOME/rcu/integration/soainfra/sql/soa_purge/soa_purge_scripts.sql

5. execute SET SERVEROUTPUT ON on SQL prompt

6. execute below SQL block and description of each variable is given below

· min_creation_date : minimum date when instance was created
· max_creation_date : Maximum date when instance was created
· batch_size :Batch size used to loop the purge. The default value is 20000.
· max_runtime :Expiration at which the purge script exits the loop. The default value is 60. This value is specified in minutes.
· retention_period :Retention period is only used by the BPEL process service engine only (in addition to using the creation time parameter). The default value is null
· purge_partitioned_component : Users can invoke the same purge to delete partitioned data.

The default value is false

DECLARE
MAX_CREATION_DATE timestamp;
MIN_CREATION_DATE timestamp;
batch_size integer;
max_runtime integer;
retention_period timestamp;
BEGIN
MIN_CREATION_DATE := to_timestamp('2011-06-23','YYYY-MM-DD');
MAX_CREATION_DATE := to_timestamp('2011-07-03','YYYY-MM-DD');
max_runtime := 15;
retention_period := to_timestamp('2011-07-04','YYYY-MM-DD');
batch_size := 5000;
soa.delete_instances(
min_creation_date => MIN_CREATION_DATE,
max_creation_date => MAX_CREATION_DATE,
batch_size => batch_size,
max_runtime => max_runtime,
retention_period => retention_period,
purge_partitioned_component => false);
END;

Here is very important to note that this script provided is able to delete instances from database schema however it will not free up the memory of that table / tablespace.

For freeing up the memory you can try this option below on tables.

alter table enable row movement.
alter table shrink space;

SOA Admin - Requirement for Weblogic / SOA Administrators

2012-10-17T20:02:00.001+05:30

Urgent Requirement for Weblogic Administrator

We have an Urgent Requirement for Weblogic Admin for Reputed MNC client

Designation : Weblogic Administrator

Location : Hyderabad

Experience : 4+ Years

Salary : As per Industry Standards

Interested Candidates can forward their updated profiles to rnstech.fmw@gmail.com.

Urgent Requirement for SOA/OSB Administrator

We have an Urgent Requirement for SOA / OSB Admin for Reputed MNC client

Designation : SOA / OSB Administrator

Location : Bangalore

Experience : 3 to 4 Years

Salary : As per Industry Standards

Vacancies : 3+ immediate

Notice Period : 10 to 15 days

Interested Candidates can forward their updated profiles to rnstech.fmw@gmail.com.

Oracle SOA Administration Training in Hyderabad

2012-10-14T22:24:00.001+05:30

About Us:

Rise 'n' Shine Fusion Middleware Technologies is a leading training and consultancy which aims to become the best education training institute especially for Admin Group who are trying to learn Oracle Fusion Middleware products. It offers MNC environment and infrastructure student's benefits with the facilities of working in real time environment and provide the best services in all the categories we deal with.

Why we are different?

Class Room & Online Training:

We offer MNC environment with excellent real time infrastructure as per student's benefits and the facilities.

Lab facilities with expert lab co-ordinators.

Our course curriculum also contains training for interview handling techniques and exclusive seminars on industry oriented awareness programs by domain experts.

Our trainers are specially recruited from IT majors.

The availability of this resource along with extreme cost-effective nature of our flexible training module should give your company a cutting edge.

Corporate Training:

For the corporate it is a mix of software packages and platforms, ranging from the low-end to the high end. And for an equally varied clientele, that include medium and large, private as well as public enterprises and software development companies.

Our training division is supported by the placement cell, which helps the candidates on attend interview in IT majors and become successful.

For more info... Rise 'n' Shine Technologies

Weblogic Admin Interview Questions-Part 3

2012-07-06T00:26:00.002+05:30

1. What is domain in WLS ? how to create a domain in WLS ?

2. What is CONFIG.XML ?

3. What is cluster and how to create a cluster in WLS ? how to configure cluster in webserver / PROXY ? tell complete configuration ?

4. What kind of PROXY u are using in your project ?

5. What is SSL and how to provide security ? what is certificate ?

6. What is one way SSL and two way ssl ?

7. How to generate certificates ? where you can store certificates ?

8. What is THREAD DUMP , why thread dump is necessary in which scenario we will be taking thread dump ?

9. How do u take thread dump ?

10. What is performance tuning ? how do u tune the performance step by step procedure ? ANS : tell from OS Lever to Our Application Level

11. What is HEAP and how to increase it ?

12. What is OOM problem / memory leak , how to overcome this problem ?

13. Complete trouble shooting steps ?

14. How to provide the security in proxy ?

15. Can you create Admin Server and managed servers in a single machine ?

16. Project architecture ? which architecture you are using ? (DMZ)

17. Which JVM you used ?

18. What is HS_ERR_PID<>.log

19. What is server log ?

20. How to provide JDBC log ?

21. How view log files in linux ?

22. Recovering admin password ?

23. How to open a file in UNIX ?

24. What certificate chaining ?

25. Session stickness ?

26. What is the use of multi cast ID ?

27. What will be there in Access Log ?

28. What is the use of boot.properties file ?

29. JMS ?

30. Connection pooling and how to create connection pool ?

31. Which performance tool you are using for monitoring the performance WLS ?

32. How to verify the network performance in any OS ?

33. Application is working but the DB is not supporting what kind of exception u will get ?

34. How to deploy an application through command line ?

35. How to check CPU utilization in UNIX ?(top)

36. How to check the disk space in UNIX ? (df –k)

37. What is node manager and what is use of it ?

38. What is garbage collection ?

39. What are the variables of the HEAP SIZE ?

40. What is head and tail command ?

41. What is Certificate Signature Request ?

42. What is the default port of the node manager ?

43. How do u find the port number is used by some the other server ?

44. What are the deployment stages ?

45. tesstart command ?

46. what is the role of JNDI ?

47. what is difference static and dynamic deployment ?

48. how do u know which thread is executing and how much time it will take ?

49. How do u give the prevalization to users and groups in UNIX?

50. Url Rewriting in weblogic?

51. What is VMSTAT command in sun Solaris?

52. How do you find port numbers in Linux?

53. What is the use of netstat command?

54. Daily activities?

55. How do u monitoring the CPU Utilization?(top or sar)

Ans: # sar -u 12 5 ` Where,-u 12 5: Comparison of CPU utilization; 12 seconds apart; 5 time

57. How the sar command shows the out put?

58. Questions on SSL(Complete)?

59. Did u attend any calls with u r clients?

60. What are Handling Disaster Recovery and Failover activities?

61. What are the things you did if the database server fails?

62. From where you are getting the trail certificates?

63. How much size you for the key generation?

64. HOW we configure SSL in proxy?

65. How we view the log files?

66. Which tool you are using for building an application?

67. What is your admin level? (L2)

68. Can we create two admin servers in a single domain?

69. What are the disadvantages of connection pooling?

70. Could you explain folder structure in bea?

71. How can we verify file size in Linux?(du –sh)

72. Why connection pooling?

73. What are the difference between authentication and authorization?

74. What are the role, user and principle?

75. Why clustering in weblogic?

76. Did you prepare any documentation as solved the any problem?

77. If you don’t have any work what can you do at that time?

78. How many machines are using in your project?

79. Can you explain your project flow? How it takes requests and give response to the clients?

80. How to generate jdbc log files?

81. If config.xml file is lost at runtime what is the solution to run the application successfully?

82. Explain different deployment stages in weblogic?

SOA 11g - JVM Tuning

2012-07-04T07:54:00.002+05:30

Installed couple of 11g SOA Suite instances and delivered it to our development team to work on it. For a week the server seemed to be working fine but then started my nightmare. The servers started becoming unstable.

Following were the issues:

1. The servers became too slow, especially the EM console hence making it difficult for developers to continue working.

2. EM Login page got struck at the user authentication page.

3. Data sources went into suspended state hence bringing EM application to halt.

4. Out of Memory issues

This is where I did have a look into the JVM settings for the SOA application. Till now I was going with default JVM settings as provided by Oracle. I generated some gc logs and used a GC analyzer to view the GC info. That is where I could see frequent GCs with unarguably high pause time. I needed to tune my JVM settings for sure.

With release of the Oracle Fusion Middleware 11g products like SOA suite, BAM, OER, OSB etc a lot has changed the way these products are built and work. Let’s focus on the SOA Suite. The 11g SOA Suite unlike the 10g now runs on Oracle Weblogic server. The SOA suite application now grows bigger with addition of applications like B2B, BAM etc. In the past releases (10g) B2B and BAM used to be separate installations .On top of this there are two management consoles, the Weblogic Admin Console and the Enterprise Manager FMW console which the product needs to function. Hence as you see the new 11g SOA suite is not only new but also a big. The Application Sever (Weblogic) has to be tuned appropriately in order to ensure a healthy SOA instance.

Below is my environment info:

Application and Database Server hardware Info

The SOA Application and the database servers both were installed on separate physical boxes. The specifications of the boxes are mentioned below.

Server Hardware: SUN T 5240 Operating System: Solaris 10 Architecture: Sun Sparc 64 Bit

Number of CPU: 10 Available Memory: 13.6 GB

Application Installed and Version:

Application Server: Oracle Weblogic Server (Version 10.3.4 )

FMW Product: Oracle SOA Suite (Version 11.1.1.4)

JVM Used: Sun JDK 1.6 Update 23

(Latest Sun JDK ,this version boasts of performance boost on Solaris servers)

Application Install Architecture: Stand Alone Install.

Below is my JVM setting recommendation. Please note, below tuning might be a good one to start with. As number of concurrent users, deployed applications, load increase the tuning parameter below might change.

SOA Suite 11g ideally uses two JVMs to function.

1. Admin Server JVM: This is the weblogic server (JVM) on which the Weblogic Admin Console and the EM Fusion Middleware Control are deployed. The Weblogic Admin Console is used to manage and control the weblogic resources. The EM Fusion Middleware control mainly is used to work on the SOA suite. It enables application deployment, application monitoring etc.

2. SOA Managed Server: This is the weblogic server (JVM) on which the entire SOA Suite and B2B product stack is deployed. Hence you can expect it to be a bit heavier than the Admin Server.

Below is the JVM settings I recommend:

JVM Heap Recommendations for Development Managed Servers

-server –d64 –Xss256k –Xms4g –Xmx4g –XX:NewRatio=2 -XX:+AggressiveOpts -XX:PermSize=1g -XX:MaxPermSize=1g -XX:+UseParallelGC -XX:+UseParallelOldGC -XX:ParallelGCThreads=8 -XX:InitialSurvivorRatio=10 -XX:SurvivorRatio=10 -XX:LargePageSizeInBytes=4m -Dweblogic.management.discover=false -Dweblogic.StuckThreadMaxTime=900 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp/java.hprof -verbose:gc -Xloggc:/tmp/gc.log -Xnoclassgc -XX:TargetSurvivorRatio=90 -XX:ReservedCodeCacheSize=64m -XX:CICompilerCount=8 -XX:+AlwaysPreTouch -XX:+PrintReferenceGC -XX:+ParallelRefProcEnabled -XX:-UseAdaptiveSizePolicy -XX:+PrintAdaptiveSizePolicy -XX:+DisableExplicitGC

JVM Heap Recommendations for Production Managed Servers

-server –d64 –Xss256k –Xms6g –Xmx8g –XX:NewRatio=2 -XX:+AggressiveOpts -XX:PermSize=2g -XX:MaxPermSize=2g -XX:+UseParallelGC -XX:+UseParallelOldGC -XX:ParallelGCThreads=16 -XX:LargePageSizeInBytes=4m -XX:InitialSurvivorRatio=10 -XX:SurvivorRatio=10 –XX:-UseTLAB -Dweblogic.management.discover=false -Dweblogic.StuckThreadMaxTime=900 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp/java.hprof -verbose:gc -Xloggc:/tmp/gc.log -Xnoclassgc -XX:TargetSurvivorRatio=90 -XX:ReservedCodeCacheSize=64m -XX:CICompilerCount=8 -XX:+AlwaysPreTouch -XX:+PrintReferenceGC -XX:+ParallelRefProcEnabled -XX:-UseAdaptiveSizePolicy -XX:+PrintAdaptiveSizePolicy -XX:+DisableExplicitGC

JVM Heap Recommendations for AdminServer

Modify the AdminServer JVM since it's running both the WebLogic Console administration application and the Enterprise Manager Fusion Application Control:

-server –Xms2g –Xmx2g –XX:NewRatio=3 -XX:+AggressiveOpts -XX:PermSize=512m -XX:MaxPermSize=512m -XX:+UseParallelGC -XX:+UseParallelOldGC -XX:ParallelGCThreads=16 -XX:InitialSurvivorRatio=10 -XX:SurvivorRatio=10 -Dweblogic.StuckThreadMaxTime=900 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp/java.hprof -verbose:gc -Xloggc:/tmp/gc.log -Xnoclassgc -XX:TargetSurvivorRatio=90 -XX:ReservedCodeCacheSize=64m -XX:CICompilerCount=8 -XX:+AlwaysPreTouch -XX:+PrintReferenceGC -XX:+ParallelRefProcEnabled -XX:-UseAdaptiveSizePolicy -XX:+PrintAdaptiveSizePolicy -XX:+DisableExplicitGC

Tuning Explanations:

The production recommendation differs from Development by the size of the heap. Since the Production environment will be hosting significantly more traffic it will need the additional heap space to grow and handle those requests. Tuning will be required in that there’s a possibility the Production SOA applications may need more or less heap space as required by the following factors:

- Size of SOA interfaces deployed - Frequency of SOA interface usage or # of instances per minute - Length of time through which each instance executes

Tuning the environment should be not speculative but a measured one. Using Memory and GC analyzing tools like Oracle Enterprise Manager Grid Control in conjunction with Performance Load Testing activities, you will be able to tune your production environment adequately to prevent any load related outages. Further tuning may need to be monitored on the JVM for Garbage Collection times. If the time it takes to do partial or Full GC increases significantly then increase the number of ParallelGCThreads. By default the ParallelGCThreads is set to what’s available at the system level. Example on a 2xUltraSPARC T2+ [T5240] = 128 which is too high and can cause heap fragmentation.

Since garbage collection in the Old Space or Tenured Space can be costly requiring more pause time and cpu time to complete a full gc, you may need to size up the New, Nursery, or Eden Space. This is controlled with the NewRatio=n directive. This sets the Eden Space to 1 / n + 1 size of the Max heap space. If you find that majority of objects are short lived meaning the heap grows to a high end with heavy load but then returns to a lower level, then you may benefit from a larger Eden space. This may require using a different directive than NewRatio. You may need to size your Eden space to 50 – 60% of the total heap size. Try –XX:NewSize=5g –XX:MaxNewSize=5g where –Xmx8g.

The default 64bit thread stack size is 1024m under SPARCv9. When defining a 64bit model [-d64] be sure to size down the thread stack size which by default is too large; the 32bit model defaults to 512k on SPARCv9; the Linux x86-64 the Java 32bit model is 256k. Some performance benchmarks on spec.org for WebLogic set the thread stack size to 128k on the Sun T series servers. Having a high thread stack size can waste a significant amount of stack space [heap space]. Consider setting it to –Xss128k or –Xss256k to free up heap space and thereby reducing the overall max heap the application may need under load.

Thread local portions of the heap in the young generation is free space on the thread stack. This can be used as a cache and can offer “excellent speedups on smaller numbers of threads (100s)”. However, this can become a burden to the JVM costing more gc time when the number of threads are in the thousands. On the Solaris SPARC platform the directive –XX:+UseTLAB is on by default. When testing an application under heavy load using thousands of threads and experiencing excessive gc, consider turning off TLABs: -XX:UseTLAB

When sizing the JVM heap or internal heaps ensure you set both the min and max to the same size. This reduces latency while the JVM is trying to size up or down the heap spaces. Example NewSize, MaxNewSize or PermSize, MaxPermSize

-XX:+HeapDumpOnOutOfMemoryError This directive creates a Heapdump in case of a out of memory error in the JMV. This would allow you to diagnose the root cause of thr memory leak.

-XX:HeapDumpPath=/tmp/java.hprof : This creates the Heapdump in the specified location.

-verbose:gc -Xloggc:/tmp/gc.log : This option allows you to specify the gc log file location.

Above tuning recommendations could be applied to other FMW products as well. Again the above recommendations should give you a descent start. With growing load and usage you may reconsider the tuning.

Weblogic 11g - WL console mode (32 bit) Installation

2012-06-29T00:37:00.000+05:30

Cd to the folder where you want to install bea – example /usr/local/

bash-3.00$ ./installfiles/server1035_solaris32.bin -mode=console

Extracting 0%....................................................................................................100%

Welcome:

This installer will guide you through the installation of BEA Products. Type "Next" or enter to proceed to the next prompt. If you want to change data entered previously, type "Previous". You may quit the installer at any time by typing "Exit".

Enter [Exit][Next]>

Choose BEA Home Directory:

"BEA Home" = [Enter new value or use default "/home9/bea"]

Enter new BEA Home OR [Exit][Previous][Next]> /usr/local/bea

Choose BEA Home Directory:

"BEA Home" = [/usr/local/bea]

Use above value or select another option:

1 - Enter new BEA Home

2 - Change to default [/home9/bea]

Enter option number to select OR [Exit][Previous][Next]>

Choose Install Type:

Select the type of installation you wish to perform.

->1|Complete

| Install the following software products and examples:

| - WebLogic Server

| - Workshop for WebLogic Platform

2|Custom

| Choose software products and components to install and perform optional configuration.

Enter index number to select OR [Exit][Previous][Next]> 2

Choose Components to install:

-----------------------------

Release 10.3.5.0

|_____WebLogic Server [1] x

| |_____Server [1.1] x

| |_____Server Examples [1.2] x

| |_____Server Add-ons [1.3] x

|_____Workshop for WebLogic Platform [2] x

|_____Workshop [2.1] x

|_____Workshop Examples [2.2] x

Enter number exactly as it appears in brackets to toggle selection OR [Exit][Previous][Next]> 2

Choose Components to install:

-----------------------------

Release 10.3.5.0

|_____WebLogic Server [1] x

| |_____Server [1.1] x

| |_____Server Examples [1.2] x

| |_____Server Add-ons [1.3] x

|_____Workshop for WebLogic Platform [2]

|_____Workshop [2.1]

|_____Workshop Examples [2.2]

Enter number exactly as it appears in brackets to toggle selection OR [Exit][Previous][Next]> 1.2

Choose Components to install:

-----------------------------

Release 10.3.5.0

|_____WebLogic Server [1] x

| |_____Server [1.1] x

| |_____Server Examples [1.2]

| |_____Server Add-ons [1.3] x

|_____Workshop for WebLogic Platform [2]

|_____Workshop [2.1]

|_____Workshop Examples [2.2]

Enter number exactly as it appears in brackets to toggle selection OR [Exit][Previous][Next]> 1.3

Choose Components to install:

-----------------------------

Release 10.3.5.0

|_____WebLogic Server [1] x

| |_____Server [1.1] x

| |_____Server Examples [1.2]

| |_____Server Add-ons [1.3]

|_____Workshop for WebLogic Platform [2]

|_____Workshop [2.1]

|_____Workshop Examples [2.2]

Enter number exactly as it appears in brackets to toggle selection OR [Exit][Previous][Next]>

Choose Product Installation Directories:

----------------------------------------

BEA Home Directory: [/usr/local/bea]

Product Installation Directories:

"Default Product Home" = [Enter new value or use default "/usr/local/bea/wlserver_10.3"]

Enter new Default Product Home OR [Exit][Previous][Next]>

Installing files..

0% 25% 50% 75% 100%

[------------|------------|------------|------------]

[***************************************************]

Installing JDK....

0% 25% 50% 75% 100%

[------------|------------|------------|------------]

[***************************************************]

Performing String Substitutions...

Creating Domains...

[Exit]>

bash-3.00$

Weblogic 11g - Performance & Tuning using JVisualVM

2012-05-28T10:14:00.000+05:30

Monitoring Remote JVMs Using JVisualVM

Real-time monitoring of a SOA/ADF 11g server Sun JVM can be provided by several tools. VisualVM is a tool that provides a visual interface for viewing detailed information about Java applications while they are running on a Sun Java Virtual Machine (for JRockit we would use JRockit Mission Control). VisualVM has features of use to application developers, system administrators, quality engineers and application users. Below are some of its key functions and features.

Display local and remote Java applications.
Display application configuration and runtime environment.(You can see the JVM startup parameters and properties)
Monitor application memory consumption and runtime behavior(Heap/Non Heap usage and GC Info)
Monitor application threads.(Displays number of threads in JVM, their status ie Running, Sleeping, Inactive, Deadlock)
Profile application performance or analyze memory allocation (Used to troubleshoot Memory Leak and OOM Issues)
§ Take and display thread dumps (Can be used to troubleshoot performance issues)
§ Take and browse heap dumps.(Used for troubleshooting Memory Leaks)
§ Analyze core dumps and applications offline.

This tool is available in the HotSpot JDK installation $HotSpot_JDK_INSTALL/bin. It is started by running the jvisualvm executable. JVisualVM can be run either on the same machine on which the SOA/ADF server runs or on a separate machine from the SOA runtime server.

Monitoring Local JVMs using JVisualVM:

If you are running JVisualVM on the same machine, on which SOA/ADF JVM runs, the setup is quite simple and straight forward. You simply have to go to the $JAVA_HOME/bin and run the jvisualvm executable. As shown below under the Local icon you can find the local JVM process PIDs and the needed information. Double click on any one of the processes under Local icon and on the right hand side of the screen you would be able to see the desired information (described later)

Monitoring Remote JVMs using JVisualVM:

If running JVisualVM from a remote machine, i.e. a JDK that is remote to the SOA Managed Server you will need to configure a JMX port in the JVM startup parameters in order to monitor the SOA/ADF server JVM. Below are the steps:

1. Configure a JMX port.

Add the below -Dcom.sun.management.jmxremote parameters to the SOA/ADF Managed Server JVM startup parameters.Keep in mind that you only want to define this for a specific server in the domain since reuse of the JMX port number between servers will not be allowed. For example if you want to monitor the JVM on soa_server1 you could add the following to its JVM startup parameters:

-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=8500 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder

So after adding the above parameters the JVM startup parameters would look like:

-server -d64 -Xss256k -Xms1g -Xmx1g-XX:NewRatio=2 -XX:+AggressiveOpts -XX:PermSize=512m -XX:MaxPermSize=512m -XX:+UseParallelGC -XX:+UseParallelOldGC -XX:ParallelGCThreads=16 -XX:InitialSurvivorRatio=10 -XX:SurvivorRatio=10 -Dweblogic.management.discover=false -Dweblogic.StuckThreadMaxTime=900 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp/soa_server1_gc.hprof -verbose:gc -Xloggc:/tmp/soa_server1_gc.log -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=8500 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder

2. Restart the SOA/ADF Managed Server (The JVM parameters of which were modified in Step 1)

3. Download and install JVisualVM from here on your local machine.

4. Open the Command Prompt on your Local Machine and navigate to the JAVA_HOME/bin as shown below. Enter the command as shown. You can also pass JVM parameters after a -J, for example to set the maximum PermSize to 256MB:

The JVisualVM Console:

5. Install All of the Available Plug-ins Select Tools -> Plugins download and install all of the available plugins, this will give additional display tabs once connected to a JVM. Restart JVisualVM, going back into Tools -> Plugins -> Installed Tab should show all of the installed plug-in:

6. Create a Remote Connection if Running JVisualVM Remotely from the SOA Server

Select the Add Remote Host icon:

7. Enter the Hostname of the server on which the SOA/ADF managed server is running. Display name can be anything related to the physical server. I chose it to be TEST_ADF_Server)

8. Right click on Test_ADF_Server under Remote icon and click on Add JMX Connection.

9. After the : in the Connection field enter the defined JMX port of 8500, this is from Dcom.sun.management.jmxremote.port=8500 also check the Display name box(Can be the JVM name):Click OK

10. After few seconds you should find the Display name(You specified in the previous step under the TEST_ADF_Server icon.

11. Right Click and click on Open. On the right hand side page you should find the JVM details as shown below.

Hurray !! You are now connected to the remote JVM via your local JVisualVM.

You can explore all of the tabs provided, these seem to be the most useful:Some of them are mentioned below:

1. The Monitor tab:

Provides the following graphs of the running system:

Also there is a Perform GC button to force a garbage collection and a Heap Dump button to cause a heap dump. The resulting heap dump will be eventually loaded into JVisualVM in a new tab where it can be analyzed. The loading may be slow and perhaps not as detailed as one would like. It may be a better idea to take heap dumps from the command line from the JDK installation where the SOA server is running:

The Threads tab:

The VisualGC Tab:

It might report you the below issue(Not Supported for the JVM)

This issue occurs when there is a version mismatch between You will get this if the JDK running JVisualVM and the SOA server are not the same version or if the operating systems do not matchMake sure you use the same version of JDKs.

This tab provides a visual representation of the memory Spaces being used in real-time in the PermGen, Old Gen, Eden Space, and Survivor Spaces (S0 & S1). This gives an idea of how how full each partition is at any given time. You can use this to scale the defined memory for the spaces based on actual load.The Graphs section also provides information on the maximum and current sizes of the spaces and their garbage collection statistics.

Conclusion

So in the post I basically have shown how would you use JVisualVM to connect to remote as well as local SOA ADF JVMs. Hope this post was helpful. I havent covered the basics and functions of jvisual vm in detail as there are too many posts already.

When it comes to SOA Heap dumps, the heap dumps generated might grow very large.The Heap Dump analysing part in jvisualvm might not work well on large jvms(greater than 3 GB). For such JVM heap analysis I would suggest you take manual dumps using jmat and analyse the dump using eclipse memory analyser. I am currently trying this in my lab and will post my updates soon.

UNIX Commands Part 2: The vi text editor

2012-04-22T00:00:00.000+05:30

Introducing vi:

The vi text editor uses two main modes: command mode and insert mode. The first part of this tutorial focuses on navigating a file, which is done in command mode. When you're in command mode, normal key presses are used to execute commands rather than to create text. When you enter insert mode, the keyboard is used to enter text, for instance, on the command line. To exit command mode, press the Esc key.

Commands in vi can be either single key presses, combined key presses using Shift or Ctrl, or key sequences. Any time a capital letter is referenced for a command, you should use the Shift key combined with that letter. Any time a command is referenced that uses two letters or symbols, you press the keys in sequence rather than simultaneously.

To begin, you'll create a blank file by opening vi from the command line followed by the name of your new file. In this tutorial, you make a document from scratch in vi and edit the document to learn useful vi commands. By the end of the tutorial, you'll have learned all the major vi commands that are used in day-to-day editing, as well as some powerful commands that you can leverage when the time is right.

$ vi tutorial.txt

vi opens with a new blank file called tutorial.txt You'll immediately notice something odd: The far left column of the text editor is filled with tilde characters. Don't worry --that's how vi illustrates undefined portions of the document. In other words, these lines don't exist yet, because the file has no content.

Before you do anything else, you should learn how to save a file and how to exit vi. These types of commands are entered by pressing the colon key followed by a sequence of letters describing your desired action. To save your new file, press the colon key, press the w key, and then press the Enter key. To quit vi, press the colon key, the q key, and the Enter key. Now, open vi again on the command line. If you try to exit vi without saving your changes, it warns you to press the exclamation point key to confirm your action. Any time you want to override a system warning, append your key sequence with an exclamation point; the key sequence to quit is : key, q key, ! key, Enter key

You can combine commands, such as wq, to save the file and then exit vi.

The first thing you need to do is insert some text so that you can learn to edit and manipulate your file. By default, you start in command mode. So, if you just start typing, you might be surprised by the results. Each mode is described in detail later; for now, press the i key to enter insert mode, and then type a few lines of text as you would in a normal text editor. When you're finished, press the Esc key to get back into command mode.

When you enter insert mode, the bottom line of the editor indicates you have done so Type some text lines in your example document so that you have text to work with After you press the Esc key, the cursor remains on the last character typed, and you're back in command mode. The next section teaches you how to navigate the file.

Navigating in vi:

In command mode, your keyboard becomes an interface tool, as opposed to a text-input tool. vi is designed for users that need access to all common commands while keeping their hands on the home keys (a-s-d-f and j-k-l-;) and reaching to nearby letters. The first basic operation to learn is moving the cursor. Most modern versions of vi allow you to use the arrow keys on the keyboard, but advanced vi users prefer the easily accessible keys under their fingertips, h-j-k-l:

• h and l represent left and right, respectively, which is intuitive because they bound the four navigation keys on the left and on the right.

• k moves the cursor up.

• j moves the cursor down.

You'll learn these keys quickly with muscle memory. To move the cursor to the first line of the three-line file you created, press k two times. The cursor now sits at the end of first line. Go ahead and use h-j-k-l to move the cursor to other locations in the file, but then bring it back to the end of line one.

Move the cursor back to the first line of the file with the h-j-k-l directional keys

Moving the cursor with shortcuts:

Moving within a line

Now that your cursor is at the end of first line, you might want to move it to the beginning of the line, but you don't want to click h over and over again to get there. In command mode, vi has keyboard-based shortcuts that let you navigate rapidly to various locations in the file more quickly than you could by moving your hand over to the mouse and pointing to the location in the file you want to go to, or using arrow keys to traverse spaces one by one. The first such shortcut is 0 (zero):

• To go to the beginning of a line, press 0; your cursor jumps to that location.

• To go back to the end of the line, press $. Go ahead and try it.

Now you can move one character at a time. You can also move to the beginning and end of each line, but those are two widely varying granularities. Another option is to navigate word by word. You can do so with the w and b keys:

• Pressing w moves forward one word.

• Pressing b moves back one word.

Try it by moving to the beginning of the first line (by pressing 0) and then move to the beginning of the word test by pressing w three times. Then, press b twice to get back to the word is.

You probably noticed that the w key and the b key set the cursor to the beginning of each word. You can also navigate to the end of each word by using the e key to move forward, or by pressing g. Press e to go backward.

Moving the cursor word by word with w and b is a good way to quickly navigate to a word you misspelled or would like to change

Moving from line to line:

Now, you can quickly move within a line but, as you deal with larger files, it's also important to rapidly navigate from line to line. There are a few ways to do this in vi. You can use the up and down commands (k and j), or you can use the page-up and page-down commands. Most commands in vi don't require you to press the Ctrl key, but the page-up and page-down commands are a couple of exceptions to this loose rule:

• Press Ctrl-u to go up a page.

• Press Ctrl-d to go down a page.

To quickly navigate to the beginning or end of a file, you can use gg or G:

• Pressing gg puts the cursor on the first line of the document.

• Pressing G puts the cursor on the last line of the document.

Inserting and editing in vi:

While navigating the document, you remain in command mode and use the keyboard as an interface tool to move the cursor. The next set of command mode keys provide different ways to enter insert mode, which is used to input new text into your file. You used the most basic way to enter insert mode at the beginning of this tutorial when you entered your initial text: You pressed the i key, which stands for insert. Pressing i puts you into insert mode in front of the current cursor location.

For instance, if you navigate to the beginning of the file by pressing gg, you can press i, which makes any text you enter appear prior to the text on the current line. Press gg, i, and then type I am inserting new text with i. Press the Esc key when you're finished to go back to command mode. Remember, you must go back into command mode after entering new text, or there is no way to navigate the document.

The simplest way to add new next is to use the i key to enter insert mode

The other basic method of entering new text is to use the a key, which stands for append. Using the a key puts you into insert mode, but it adds text after the current location of the cursor instead of before the current location of the cursor. To test this, go to the last line of your document and press the G and $ key to go to the end of the line. Then press the key, type Pressing a appends text, and press the Esc key to return to command mode.

Another way to insert text is with the a key, which stands for append Now your cursor is at the period on the last line of your file. If you press the i key now, you'd insert text just before the period. If you press the a key, you'd insert text just after the period. By pressing the I key (the capital letter), you can start your input at the beginning of the line, even though your cursor is at the end of the line. Similarly, if you press the capital A key, you can input text at the end of the line regardless of the cursor position. To test this, press I, type I think , and then press the Esc key.

To insert text at the beginning of a line (regardless of cursor position), press the I key Another useful way of inserting new text is to simultaneously enter insert mode and add a new line to your text file. Just like the normal text insertion, this can be done before or after the cursor location:

• To insert a new line above the current cursor location, press the O key.

• To insert a new line below the current cursor location, press the o key. To try this command, press O, type I inserted this line by pressing O, and then press the Esc key to return to command mode.

To insert text on a new line before the cursor, press the O key

You've now used the major methods of inserting new text. To recap, the keys are a, i, A, I, o, and O. Can you remember what each one does? Don't worry, even if you don't, they will come natural to you after a few days of use.

Replacing text

Now that you've typed a few items into your tutorial.txt file, you might find that you've made some errors, or you might want to change your choice of words. Before learning how to delete text, you should learn how to replace text. Why? Because if you learn to add new text and delete old text, you might fall into the habit of using the delete commands when a replace command would be more efficient. It's quicker to replace a word in a one-step process than it is to delete a word and then add a new word in its place.

vi uses two important replace commands. The first is the r key, which removes the character the cursor is focused on and puts you in insert mode for a single replacement character. In other words, you can make one keypress after pressing r. As a result, vi automatically returns to command mode (without pressing the Esc key). To try this, use the k key and the l key to navigate up to the end of second line. Your cursor should be focused on a period. To change the period to an exclamation point, press the r key and then press the! Key.

To replace a single character, press the r key and then type the character you want in the document

An even more useful replacement command is executed by pressing the c key and then the w key, which together stand for change word. This command deletes the current word and puts you in insert mode so that you can immediately start typing a replacement word. In this case, you need to press the Esc key when you're finished typing the new word to let vi know you're done. Move down to the word great, press the c and w key, type cool, and then press the Esc key.

To replace a word, press the c and w key and then type the new word

If you want to remove text altogether rather than replacing it, you need to use a delete command. As with many other things in vi, you have multiple choices, depending on how much data you want to delete at once. The most basic delete command is the x key, which deletes one character at a time. To try it, go back to the beginning of your text file and press the Ctrl-u (page-up) key. Press the $ key to go to the end of the line and then press the x key five times to delete the test.

Deleting text

To delete individual characters, use the x key

Pressing the x key five times did the job, but you've probably gathered that vi has a quick way of doing just about everything. You can delete a word with one command by pressing the d key and w key, which together stand for delete word. Navigate back to the word This by pressing the b key three times. To delete the word, press the d key and w key.

To delete individual words, use the dw command

You're left with a hanging, partial sentence at the end of the first line. To delete everything on a line that follows your cursor position, you can use the d key with the $ key, which you've learned is used for end-of-line operations. Press the d key and the $ key to remove is a from the end of the line.

To delete from the cursor to the end of a line, use d$

The final commonly used deletion method in vi is the delete-line command, which is accomplished by pressing the d key twice. It deletes the text on the line and brings the next lower line up, so you don't have an empty line in the document. To remove the first line of your file, press the d key and then press the key again.

To delete an entire line, press dd.

Speaking of bringing up a line, you can use the join command by pressing the J key, which brings the line below the cursor up to the line the cursor is on, without deleting any text. Your cursor should be on the new line (line 1) of your document.

Press the J key to bring line 2 up to line 1. To bring two lines together in vi, press the J key

Getting fancy:

You should now have the basic skills to create, navigate, and edit a text file in vi. After you get familiar with the basic commands, you can create and edit files about as quickly as you can in a more conventional text editor. A few things are missing from your repertoire, though. This section teaches you how to cut, copy, and paste. You can do multiple iterations of a command at one time, repeat commands, search the document, and use undo and redo. This editor meets the major functionality found in other text editors and uses the fast-access keyboard command style.

Cut, copy, and paste

In vi, any time a piece of text is deleted, it's automatically stored in a buffer (like the clipboard in Windows). You already know how to do a cut command by using x, dd, dw, and d$. Similar commands are available to copy data without deleting it --this process is called yank in vi --:

• Press the y key twice to copy a whole line.

• Press the y key and w key to copy an individual word.

• Press the y key and $ key to copy a line starting at the current cursor location.

Copying data isn't much use without knowing how to paste it. So, before testing these commands, you should learn the paste command, which is enacted with the p key. Like many other commands in vi, a lowercase p key pastes data after the cursor location, whereas an uppercase P key pastes data before the cursor position.

To copy and paste, navigate to the first line of your text file and press the y key twice. Then, move the cursor down to line 2 and press the p key once. Doing so creates a copy of line 1 on line 3.

To copy a line, use the yy command and paste using the p command.

Try doing a cut and paste by moving the cursor to the second line and press the d key twice. Then, press the p key to paste the line below line 2.

To cut and paste a line, use the dd command and the p command

Using numbers to preface vi commands

At this point, you might wonder how to do some of these commands on more than one piece of data at a time. For instance, you probably often copy and paste entire paragraphs, as opposed to single lines. vi lets you preface just about every command in the application with a number, which causes the command to operate multiple times at once. This is an extremely powerful, important part of what makes vi a great editor for power users. To try a simple example of cutting and pasting two lines at a time, navigate to line 1 of the file, press the 2 key, press the d key twice, and then press the p key.

Cut and paste two lines at a time by using a number 2 preceding the dd command and the p command

The same concept can be used during the paste command to replicate a line multiple times. To do so, go back to line 1, copy the line with the yy command, and then press 10 before pressing the p key. Now you have 10 more lines of comments about vi. Before moving on, press the 5 key and then press the d key twice to remove some of the extra lines.

Paste multiple lines by preceding the p command with the number 10; then delete some of them with the number 5 preceding dd

Experiment with numbers in front of navigation commands as well. For instance, pressing the 30 key and then the l key moves the cursor 30 spaces to the right. Pressing the 7 key and then the G key moves the cursor to line 7 in the file. Pressing the 5 key and then the w key moves the cursor to the fifth word. When you're finished experimenting, you can move on to the next step.

Repeating vi commands

Another useful command in vi is executed with the . (period) key. The . key repeats the last command, which is an important feature for getting work done quickly. For instance, navigate the cursor to the word cool on the first line, and then use the cw command to change the word to fast. Don't forget to press the Esc key when you're finished typing the word fast. Move down to another instance of the word cool, and then press the . key to change that word to fast. You can also move to the word line on the last two lines of your file and replace those with the. key.

Repeat commands with the period key, which lets you produce document edits quickly

Searching text in vi

Searching text in vi is also fast and efficient. To start searching for a string, press the / key (slash key) followed by the string you want to search for and then press the Enter key. To combine some of your vi skills, press the / key, type think, press Enter, and then use the cw command to change the word to know. Don't forget to press the Esc key when you're finished.

If you want to do the same thing on line 2, press the n key to find the next instance of think, and then press the . key to change the word to know. The ? key does a search just like the / key, but it searches the document backward instead of forward.

After you've replaced think with know, press the ? key followed by the word fast to search back to it.

Search for strings by using the slash key followed by the string you're searching for

Search for strings backward by using the ? key followed by the string you're searching for

Undo and redo in vi

If you make any mistakes, vi has the modern convenience of undo and redo to make sure you can restore your document to the proper state. Undo is accomplished by pressing the u key in command mode, and redo is executed by pressing Ctrl-r in command mode. Try undo and redo, as follows:

1. Go to line 3 in your text file and remove a few lines.

2. Press the 3 key and the G key to go to line 3.

3. Press the 2 key and the dd command to delete two lines.

4. Oops! That was a mistake, and you want to get the two lines back. To do so, press the u key to undo the previous command.

5. If you change your mind and want the two lines removed, press Ctrl-r to redo the command.

To undo a command, use the u key; to redo a command, press Ctrl-r

Wrap-up:

To wrap up, run though a last sequence of commands to combine some of the things you've learned:

1. To go to the beginning of your document, press the g key twice.

2. To delete everything in your file (because you have less than 100 lines), type 100 followed by the dd command.

3. Press the i key to go into insert mode.

4. Type I am done with this tutorial!.

5. Press the Esc key.

6. Press the y key twice, type 100, and then press the p key.

You've now yelled to your computer 100 times that you're done! Good job; time for a break and a cup of coffee.

After working through this tutorial, you should have the knowledge to create and edit files with vi. Experiment with the commands listed throughout this tutorial, and practice them by beginning to use vi as your day-to-day text editor. It will slow you down at first but, in a short time as you memorize the commands and learn when and where to use them, vi can significantly increase your productivity.

UNIX Commands Part 1: File Maintenance tools

2012-04-20T00:42:00.001+05:30

Log in to the UNIX-like operating system of your choice to get started. When you log in, you should automatically start in your user's home directory. The examples use the tuser (Test User) username.

man: man stands for manual;

$ man ls

ls:

$ ls

$ ls -l

$ ls -a

$ ls -R

cd:

$ cd Documents

$ cd /tmp

$ cd /home/tuser

Special directory names

$ cd ..

$ cd ~

pwd:

$ pwd

mkdir, rmdir:

$ mkdir TUTORIAL

$ cd TUTORIAL

$ pwd

$ ls

$ cd ~/TUTORIAL

$ pwd

Directory layout:

/home (or /users)

/etc

/bin

/sbin

/usr

/car

/tmp

Files -

touch:

$ cd ~/TUTORIAL

$ touch example.txt

cp:

$ cp example.txt /tmp/

$ ls /tmp/

$ cp /tmp/example.txt ./example2.txt

$ ls

mv:

$ mv example2.txt /tmp/.

rm:

$ rm /tmp/example.txt

$ rm /tmp/example2.txt

$ ls /tmp/

Ownership and permissions

chown, chgrp:

$ man chown

$ man chgrp

$ chown tuser example.txt

$ chgrp admin example.txt

chmod:

$ ls -l

-rw-r--r--1 tuser admin 0 Aug 13 15:35 example.txt

----------1 tuser admin 0 Aug 13 15:35 example.txt

A file that has all permissions turned on reads this way:

-rwxrwxrwx 1 tuser admin 0 Aug 13 15:35 example.txt

$ man chmod

$ chmod og-r example.txt

$ ls -l

You should see this result:

-rw-------1 tuser admin 0 Aug 13 15:35 example.txt

Dealing with multiple files -

$ cp example.txt example2.txt

$ cp example.txt script.sh

$ ls *.txt

$ ls exa*

Recursion:

$ cd ~

$ cp -R TUTORIAL /tmp/.

$ ls /tmp/TUTORIAL/

$ rm -R /tmp/TUTORIAL/

$ ls /tmp/

Archives and compression -

tar:

$ cd ~

$ tar cvf /tmp/tutorial.tar TUTORIAL

$ ls /tmp/

$ ls

$ tar cvf tutorial

$ ls

$ rm -R /tmp/TUTORIAL

gzip:

$ gzip tutorial.tar

$ ls

$ gzip -d tutorial.tar.gz

The file system and file sizes:

df:

$ df -h

$ ls -lh

du:

$ cd ~

$ du -sk *

$ du -sh *

mount:

$ mount -t iso9660 /dev/cdrom /mnt/cdrom

$ df

$ ls /mnt/cdrom

umount:

$ umount /mnt/cdrom

$ df

$ ls /mnt/cdrom

Redirection

$ cd ~/TUTORIAL

$ ls > listing.txt

$ ls

cat:

$ cat listing.txt

$ ls /etc/ > listing2.txt

$ cat listing2.txt

$ more listing2.txt

head and tail:

$ head listing2.txt

$ tail listing2.txt

$ head -n 2 listing2.txt

grep:

$ grep host listing2.txt

pipe:

$ ls /etc/ | grep host

$ du -sh /etc/* | more

Weblogic 11g - Enable automatically back up configuration (config.xml)

2012-04-06T00:16:00.000+05:30

Check how to set Weblogic take automatically back up of you configuration (config.xml file)

Login to weblogic console
Click Domain –> Configuration –> General (Advanced)
Check Configuration Archive Enabled and Count.
true - backups of the configuration will be made during server boot.
Change will take place after you redeploy module or restart the server

it will create following files in domain.

config-booted.xml
config-original.xml

Weblogic 11g - Development Mode Vs Production Mode

2012-04-05T00:23:00.000+05:30

While configuring any Weblogic domain the there are two modes the domain can be configured with.

- Development Mode

- Production Mode

The question is how to decide which mode to use:

Let’s say you are developing your applications. The process will involve multiple redeployments to the server. In this case you would wish for a relaxed security configuration on the server. Also you would wish for features like auto deployment of your code. In such scenarios use the Development Mode.

Now consider you got your application working right, ready to go live. In this mode you would definitely wish for a full fledged security. Consider using the Production Mode here.

The differences between the two modes are stated below:

1. SSL

In development mode you can use the demonstration digital certificates and the demonstration keystores provided by the WebLogic Server security services. With these certificates, you can design your application to work within environments secured by SSL where as in Production Mode you should not use the demonstration digital certificates and the demonstration keystores. If you do so, a warning message is displayed.

2. Application Deployment

In Development Mode WebLogic Server instances can automatically deploy and update applications that reside in the domain_name/autodeploy directory (where domain_name is the name of a domain) where as in Production Mode the auto-deployment feature is disabled, so you must use the WebLogic Server Administration Console, the weblogic.Deployer tool, or the WebLogic Scripting Tool (WLST).

3. Lock and Edit Feature

In Development Mode any configuration change being done by a user doesn’t need him to take a Lock and Edit session, where as in Production Mode the user needs to procure a Lock and Edit session before trying to make any configurational changes.

Important Considerations:

-->It is recommended that this method be used only in a single-server development environment.

-->You can always switch the domain startup mode from Development to Production and Vice Versa

-->Oracle recommends usage of JRockit instead of Sun JDK in Production Mode. This recommendation depends on platform on which your domain runs. For platforms like Solaris SunJDK is recommended even in Production Mode. JRockit works well on OEL/Red hat Linux platforms.

SOA 11g - Config and Log Files Location

2012-04-05T00:12:00.000+05:30

The intent of this note is to list the important configuration and log files used to diagnose SOA 11g problems.

Throughout this note we will refer to the following:
- $ MIDDLEWARE_HOME =
- $ DOMAIN_HOME = $ MIDDLEWARE_HOME/user_projects/domains/

Here is a list of files to look for:
1.Domain configuration under $DOMAIN_HOME/config  directory
   - Config.xml
   - jdbc/-Jdbc.xml
   - jms/-Jms.xml files under

2. Adapter configuration under $MIDDLEWARE_HOME//soa/connectors/   directory. ( Oracle_SOA1 is the default name)
- AppsAdapter.rar
- DbAdapter.rar
- FtpAdapter.rar
- MQSeriesAdapter.rar
- SocketAdapter.rar
- AqAdapter.rar
- FileAdapter.rar
- JmsAdapter.rar
- OracleBamAdapter.rar

3. Admin Server log files under $DOMAIN_HOME/servers//logs directory
- Access.log
- -Diagnostic.log
- .log

4. SOA Server log files under $DOMAIN_HOME/servers//logs directory
- . log
- -Diagnostic.log
- .log

SOA 11g - Checking FMW and WebLogic Component Versions

2012-04-05T00:04:00.000+05:30

Applies to:
Oracle Fusion Middleware - Version: 11.1.1.1.0 to 11.1.1.5.0 - Release: to Oracle11g
Information in this document applies to any platform.

Goal
This document describes how to determine the versions of installed Fusion Middleware Components and Weblogic Server.

Note:
Fusion Middleware components including WebLogic Server, RCU, and components such as SOA, Identity Management, Portal-Forms-Reports-Discover, and JDeveloper must have concordant versions. This affects configuration, but not installation, and can cause a variety of failures, including ClassDefNotFound exceptions when trying to configure a new domain or managed server.

1. To determine the WebLogic Server version. There are several ways to confirm the version:

Enter this command with the weblogic environment enabled:

$ java weblogic.version

Look in the file Middleware Home/registry.xml, and note the component tag

The exact WLS version can be checked using the following commands:

On Unix:

cat $MW_HOME/wlserver_10.3/.product.properties | grep WLS_PRODUCT_VERSION

On Windows:

type %MW_HOME%\wlserver_10.3\.product.properties | findstr WLS_PRODUCT_VERSION

Use SmartUpdate to check the Product Version:

On Unix:

$MW_HOME/utils/bsu/bsu.sh -view -status=applied -prod_dir=$MW_HOME/wlserver_10.3 | grep ProductVersion

On Windows:

%MW_HOME%\utils\bsu\bsu.sh -view -status=applied -prod_dir=$MW_HOME\wlserver_10.3 | findstr ProductVersion

You should see a result such as this:

ProductVersion: 10.3 MP5

2. For JDeveloper, look in the Middleware Home/registry.xml file for the following:

3. For Fusion Middleware products, use the command Oracle Home/Opatch/opatch lsinventory and note the output:

Installed Top-level Products (2):

Application Server 11g SOA Patchset 11.1.1.3.0
Oracle SOA Suite 11g 11.1.1.2.0
There are 2 products installed in this Oracle Home.

4. For the MDS version, look in the file RCU Home/rcu/log/logdir./mds.log:

REPOS_VERSION CONSTANT VARCHAR2(32) := '11.1.1.56.27' (this is for 11.1.1.3)

To get the schema version from the database, login to the database as sysdba and enter the command as shown (example here for 11.1.1.3):

SQL> select comp_id, comp_name, version from schema_version_registry;

COMP_ID
------------------------------
COMP_NAME
--------------------------------------------------------------------------------
VERSION
------------------------------
IAU
Audit Service
11.1.1.3.0

MDS
Metadata Services
11.1.1.2.0

OID
Oracle Internet Directory
11.1.1.3.0

OIF
Oracle Identity Federation Database Schema
11.1.1.2.0

ORAESS
Enterprise Scheduler Service
11.1.1.2.0

ORASDPLS
SIP Infrastructure Location Service
11.1.1.2.0

ORASDPSDS
SIP Infrastructure Subscriber Data Service
11.1.1.2.0

ORASDPXDMS
Presence
11.1.1.2.0

8 rows selected.

You can also get the schema prefix from the database using the following command:

SQL> select username, created from dba_users order by 2;

USERNAME CREATED
------------------------------ ---------
OE 12-MAY-10
SH 12-MAY-10
BI 12-MAY-10
PM 12-MAY-10
TEST01_MDS 21-JAN-11
TEST01_IAU 21-JAN-11
TEST01_IAU_APPEND 21-JAN-11
TEST01_IAU_VIEWER 21-JAN-11
TEST01_ORAESS 21-JAN-11
ODS 21-JAN-11
ODSSM 21-JAN-11

USERNAME CREATED
------------------------------ ---------
TEST01_OIF 21-JAN-11
TEST01_ORASDPXDMS 21-JAN-11
TEST01_ORASDPLS 21-JAN-11
TEST01_ORASDPSDS 21-JAN-11

Weblogic 11g - Performance & Tuning using JConsole

2012-03-29T23:47:00.000+05:30

Jconsole is a JMX-compliant monitoring tool. It uses the extensive JMX instrumentation of the Java virtual machine to provide information on performance and resource consumption of applications running on the Java platform.

Starting jconsole
The jconsole interface
Viewing summary information
Monitoring Memory Consumption
Monitoring Thread Use
Monitoring Class Loading
Monitoring and Managing MBeans
Viewing VM Information
Frequently Asked Questions

Starting jconsole

The jconsole executable is in JDK_HOME/bin, where JDK_HOME is the directory where the JDK is installed. If this directory is on your system path, you can start the tool by simply typing jconsole in a command (shell) prompt. Otherwise, you have to type the full path to the executable file.

Command Syntax

You can use jconsole to monitor both local applications (those running on the same system as jconsole) and remote applications (those running on other systems).

Note: Using jconsole to monitor a local application is useful for development and prototyping, but is not recommended for production environments, because jconsole itself consumes significant system resources. Remote monitoring is recommended to isolate the jconsole application from the platform being monitored.

For a complete reference on jconsole command syntax, see jconsole - Java Monitoring and Management Console.

Local Monitoring

To monitor a local application, it must be running with the same user ID as jconsole. The command syntax to start jconsole for local monitoring is:

jconsole [processID]

where processID is the application's process ID (PID). To determine an application's PID:

On Unix or Linux systems, use the ps command to find the PID of java.
On Windows systems, use Task Manager to find the PID of java or javaw.

You can also use the jps command-line utility to determine PIDs.

For example, if you determined that the process ID of the Notepad application is 2956, then you would start jconsole as follows:

jconsole 2956

Both jconsole and the application must by executed by the same user name. The management and monitoring system uses the operating system's file permissions.

If you don't specify a process ID, jconsole will automatically detect all local Java applications, and display a dialog box that lets you select the one you want to monitor (see the next section).

For more information, see Local JMX Monitoring and Management.

Remote Monitoring

To start jconsole for remote monitoring, use this command syntax:

jconsole [hostName:portNum]

where hostName is the name of the system running the application and portNum is the port number you specified when you enabled the JMX agent when you started the JVM. For more information, see Remote JMX Monitoring and Management.

If you do not specify a host name/port number combination, then jconsole will display a connection dialog box (see the next section) enabling you to enter a host name and port number.

Connecting to a JMX Agent

If you start jconsole with arguments specifying a JMX agent to which to connect, it will automatically start monitoring the specified JVM. You can connect to a different host at any time by choosing Connection | New Connection. and entering the necessary information.

Otherwise, if you do not provide any arguments when you start jconsole, the first thing you see is the connection dialog box. This dialog box has three tabs:

Local
Remote
Advanced

Local Tab

The local tab lists any JVMs running on the local system started with the same user ID as jconsole, along with their process ID and class/argument information. Select the application you want to monitor, then click Connect.

Remote Tab

To monitor a remote JVM, enter:

Host name: name of the machine on which the JVM is running.
Port number: the JMX agent port number you specified when you started the JVM.
User name and password: the user name and password to use (required only if monitoring a JVM through a JMX agent that requires password authentication).

For information on setting the port number of the JMX agent, see Enabling the JMX Management Agent. For information on user names and passwords, see Using Password and Access Files.

To monitor the JVM running jconsole, simply click Connect, using host localhost and the port zero (0).

Advanced Tab

The advanced tab enables you to connect to other JMX agents (MBean servers) by specifying their JMX URL, and the user name and password. The syntax of a JMX URL is described in the API documentation for javax.management.remote.JMXServiceURL.

Note: If the JMX agent is using in a connector which is not included in the Java platform, you need to add the connector classes to the classpath when running jconsole as follow:

jconsole -J-Djava.class.path=JAVA_HOME/lib/jconsole.jar:JAVA_HOME/lib/tools.jar:connector-path

where JAVA_HOME is the directory containing the JDK and connector-path is the directory or the jar file containing the classes not included in JDK 5.0 to be used by jconsole for connecting to a JMX agent.

The jconsole interface

The jconsole interface is composed of six tabs:

Summary tab: displays summary information on the JVM and monitored values.
Memory tab: displays information on memory use.
Threads tab: displays information on thread use.
Classes tab: displays information on class loading
MBeans tab: displays information on MBeans
VM tab: displays information on the JVM

The following sections provide information on each tab.

Viewing Summary Information

The Summary tab displays some key monitoring information on thread usage, memory consumption, and class loading, plus information on the JVM and operating system.

Summary

Uptime: how long the JVM has been running
Total compile time: the amount of time spent in just-in-time (JIT) compilation.
Process CPU time: the total amount of CPU time consumed by the JVM

Threads

Live threads: Current number of live daemon threads plus non-daemon threads
Peak: Highest number of live threads since JVM started.
Daemon threads: Current number of live daemon threads
Total started: Total number of threads started since JVM started (including daemon, non-daemon, and terminated).

Memory

Current heap size: Number of Kbytes currently occupied by the heap.
Committed memory: Total amount of memory allocated for use by the heap.
Maximum heap size: Maximum number of Kbytes occupied by the heap.
Objects pending for finalization: Number of objects pending for finalization.
Garbage collector information: Information on GC, including the garbage collector names, number of collections performed, and total time spent performing GC.

Classes

Current classes loaded: Number of classes currently loaded into memory.
Total classes loaded: Total number of classes loaded into memory since the JVM started, included those subsequently unloaded.
Total classes unloaded: Number of classes unloaded from memory since the JVM started.

Operating System

Total physical memory: Amount of random-access memory (RAM) that the OS has.
Free physical memory: Amount of free RAM the OS has.
Committed virtual memory: Amount of virtual memory guaranteed to be available to the running process.

SOA 11g - SOA Admin Interview Questions 2

2012-03-25T01:58:00.003+05:30

1. How to know the Managed Servers status, when admin console is not available?

2. What is the performance issue in weblogic and how can you resolve, explain in brief?

3. What is the Digital Certificate? How do we generate a Digital Certificate?

4. What is Thread Dump? What is the UNIX command to take Thread Dumps?

5. What is a cluster? What is High Availability and Fail over?

6. How to handle out of memory in weblogic and if server is getting more requests then what we have to do in production environment?

7. What is clustering? How do weblogic instances communicate in a clustered environment? In a cluster, if one of the servers has an issue and it is not accessible, will the other servers know about it and how?

8. What are the roles you have played and what are the day today activities?

9. WHAT IS TROUBLE SHOOTING IN WEBLOGIC?

10. How to integrate apache webserver with weblogic server? What is the purpose of integrating both?

11. Define the different groups of Users?

12. What are the different thread queues?

13. How will you analyze if a page responds slowly?

14. What is Work manager? Explain briefly?

15. What are the different types of drivers?

16. What are the various types of log files?

17. What are you commonly used fine tuning commands?

18. What is Session replication? What are the different types of Session Replications?

19. What happens if we change config.xml while server is running?

20. What is HTTP tunneling?

21. What is asynchronous communication? Is there any synchronous communication in JMS?

22. How to find Weblogic Version?

23. What is the use of log4j?

24. What is Work manager?

25. What is virtual host?

26. What is eden size and perm size?

27. What is Weblogic shrink?

28. What is diff b/w JNDI and JDBC?

29. What are the different types of drivers?

30. What driver you are using?

31. What is diff b/w unicast and multicast?

32. When core dump will not be created even if the server crashed?

33. Can we change the heart beat interval?

34. What are the various types of log files?

35. What is WorkManager?

36. What is Multicast IP Address? What are the things done by it? How to

test multicast IP?

37. How to check whether the cluster multicast adress is available or not?

What is the command to check in UNIX environment?

38. What is Virtual Host in Weblogic, how to create it & what is the

advantage ?

39. How can you find the jdbc version on server side?

40. What you do to close the connections automatically in JDBC?

41. What are the things that we take care under Database fine tuning apart

from increasing or decreasing connections?

42. What is MBean, how many types are there?

43. How to restart proxy?

44. Reasons for server crash?

45. Reasons for servers hang?

46. What is the thread hogging?

47. Various garbage collection algorithms?

48. How to find whether the PORT No is free or not?

49. What is the command to find CPU utilization?

50. What is the command to find version of Unix?

51. How to find CPU utilization? What if top command doesn’t work?

52. What are you commonly used fine tuning commands?

53. What is the difference between webservers and Proxy server?

54. How to sort the files?

55. What is Session replication? What are the different types of Session Replications?

56. Which IP segment will you use for Multicasting?

57. Is it possible to manage multiple domains through a single weblogic

admin console?

58. What happens if we change config.xml while server is running?

SOA 11g - Deployment of SOA Applications

2012-03-25T00:46:00.000+05:30

Deploying SOA Applications

You can deploy SOA composite applications from Oracle Enterprise Manager Fusion Middleware Control Console with the Deploy SOA Composite wizard. Use the Deploy SOA Composite wizard to deploy any of the following:

A new SOA composite application for the first time
A new revision (for example, 2.0) alongside an older revision (for example, 1.0) without impacting the latter. The revision deployed last becomes the new default revision of that composite (unless you specify otherwise at a later step during deployment).

Deployment extracts and activates the composite application in the SOA Infrastructure. Once an application is deployed, you can perform administration tasks, such as creating instances, configuring properties, monitoring performance, managing instances, and managing policies and faults.

To deploy applications:

Access the Deploy SOA Composite wizard through one of the following options:

From the SOA Infrastructure Menu...

Select SOA Deployment >Deploy.

From the SOA Folder in the Navigator...

Right-click soa-infra.
Select SOA Deployment >Deploy.

From the SOA Infrastructure Home Page...

Click the Deployed Composites tab.
Above the Composite table, click Deploy.

From the SOA Composite Menu...

Select SOA Deployment >Deploy another Composite.

Note:

You can also access the Deploy SOA Composite wizard by selecting Deploy to This Partition from the Deployment dropdown list of the Manage Partitions page or home page of a specific partition, from the SOA Partition menu at the top of the home page of a specific partition, or by right-clicking a specific partition in the navigator.

The Select Archive page appears.

In the Archive or Exploded Directory section, specify the archive of the SOA composite application to deploy. The archive contains the project files of the composite to be deployed (for example, HelloWorld_rev1.0.jar for a single archive or OrderBooking_rev1.0.zip for multiple archives). This information is required.
In the Configuration Plan section, optionally specify the configuration plan to include with the archive. The configuration plan enables you to define the URL and property values to use in different environments. During process deployment, the configuration plan is used to search the SOA project for values that must be replaced to adapt the project to the next target environment.
Click Next.

The Select Target page appears.

This page lists the Oracle SOA Suite managed server or cluster to which to deploy the SOA composite application archive.

Select the partition into which to deploy this SOA composite application. Partitions enable you to logically group SOA composite applications into separate sections. Note that even if there is only one partition available, you must explicitly select it. Once deployed, a composite cannot be transferred to a different partition.

If you want to deploy to a partition that does not exist, exit the wizard and create the partition before deploying the composite. You create partitions in the Manage Partition page, accessible from the SOA Infrastructure menu.

If the server contains no partitions, you cannot deploy composite applications to that server. Also, if the server is not in a running state, you cannot deploy this archive. By default, a partition named default is automatically included with Oracle SOA Suite. You can delete the default partition.

Notes:

A SOA composite application with the same name can be deployed to separate partitions. Each is deployed as a distinct, separate composite from the other.
You cannot deploy the same SOA composite application with a human workflow task into multiple partitions. For example, if the composite named VacationRequest includes VacationRequestTask.task, you cannot deploy this composite into a partition named production and a partition named development. Deploy this composite to only one partition.

If you invoke the Deploy SOA Composite wizard by selecting Deploy to This Partition from the Deployment dropdown list on the Manage Partitions page or home page of a specific partition, the partition to which to deploy is already selected. Therefore, the Select Target page is skipped.

Click Next.

The Confirmation page appears.

Review your selections.
Select whether to deploy the SOA composite application as the default revision. The default revision is instantiated when a new request comes in.
Click Deploy.

Processing messages are displayed.

At this point, the deployment operation cannot be cancelled. Deployment continues even if the browser window is closed.

When deployment has completed, the home page of the newly deployed composite revision automatically displays. A confirmation message at the top of the page tells you that the composite has been successfully deployed. In the case of a bundle deployment, the Deployed Composites page of the SOA Infrastructure is displayed.

Redeploying SOA Applications

You can redeploy SOA composite applications from Oracle Enterprise Manager Fusion Middleware Control Console with the Redeploy SOA Composite wizard. Using the Redeploy SOA Composite wizard has the following consequences:

A new version of a revision of a currently deployed SOA composite application is redeployed on the same deployment target (for example, old version 1.0 is redeployed as new version 1.0).
If the older, currently deployed version of this revision has running instances, the state of those instances is changed to stale. The instance state is available in the instance listing, and you can access audit and flow trace details.

Notes:

If you want to maintain multiple revisions of a deployed application (for example, revisions 1.0 and 2.0), do not use this wizard. Instead, use the Deploy SOA Composite wizard.
Redeploying multiple SOA composite applications at once is not supported.

To redeploy applications:

Access this page through one of the following options:

From the SOA Infrastructure Menu...

a. Select SOA Deployment>Redeploy. The Select Composite page appears.

b. In the SOA Composite Deployments section, select the SOA composite application revision you want to redeploy, and click Next.

From the SOA Folder in the Navigator...

Right-click soa-infra.
Select SOA Deployment > Redeploy. The Select Composite page appears.

c. In the SOA Composite Deployments section, select the SOA composite application revision you want to redeploy, and click Next.

From the SOA Infrastructure Home Page...

Click the Deployed Composites tab.
In the Composite table, select a specific SOA composite application. Only one application can be redeployed at a time.
Above the Composite table, click Redeploy.

From the SOA Composite Menu...

Select SOA Deployment >Redeploy.

Note:

You can also access the Redeploy SOA Composite wizard by right-clicking a partition and selecting SOA Deployment > Redeploy.

The Select Archive page appears.

In the Archive or Exploded Directory section, select the location of the SOA composite application revision you want to redeploy.
In the Configuration Plan section, optionally specify the configuration plan to include with the archive.
Click Next.

The Confirmation page appears.

Select whether to redeploy the SOA composite application as the default revision.
Click Redeploy.

Processing messages are displayed.

At this point, the deployment operation cannot be cancelled. Deployment continues even if the browser window is closed.

When redeployment has completed, click Close.

When redeployment has completed, the home page of the newly redeployed composite revision is displayed. A confirmation message at the top of the page tells you that the composite has been successfully redeployed.

Undeploying SOA Applications

You can undeploy SOA composite applications from Oracle Enterprise Manager Fusion Middleware Control Console with the Undeploy SOA Composite wizard. Using the Undeploy SOA Composite wizard has the following consequences:

You can no longer configure and monitor this revision of the application.
You can no longer process instances of this revision of the application.
The state of currently running instances is changed to stale and no new messages sent to this composite are processed.
The instance state of the undeployed composite application is set to stale. The instance state is available in the instance listing, and you can access audit trail details. However, the flow trace is not available. If you click the Flow tab, a message is displayed indicating that the flow trace view is not available for undeployed composites.
If you undeploy the default revision of the application (for example, 2.0), the next available revision of the application becomes the default (for example, 1.0).

Note:

If you want to undeploy and then redeploy an existing revision of this application, do not use this wizard. Instead, use the Redeploy SOA Composite wizard. The Redeploy SOA Composite wizard enables you to redeploy an existing revision of a SOA composite application and remove (overwrite) the older, currently deployed version of the revision.

To undeploy applications:

Note:

You can undeploy multiple SOA composite applications together if they are located in the same partition.

Access this page through one of the following options:

From the SOA Infrastructure Menu...

Select SOA Deployment>Undeploy. The Select Composite page appears.
In the SOA Composite Deployments section, select a specific SOA composite application to undeploy, and click Next.

From the SOA Folder in the Navigator...

Right-click soa-infra.
Select SOA Deployment >Undeploy. The Select Composite page appears.
In the SOA Composite Deployments section, select a specific SOA composite application to undeploy, and click Next.

From the SOA Infrastructure Home Page...

Click the Deployed Compositestab.
In the Composite table, select a specific SOA composite application. Only one application can be undeployed at a time.
Above the Composite table, clickUndeploy.

From the SOA Composite Menu...

Select SOA Deployment >Undeploy.

Note:

You can also access the Undeploy SOA Composite wizard through these additional partition options:

Right-clicking a partition and selecting SOA Deployment > Undeploy From This Partition
Selecting Deployment > Undeploy All From This Partition on the partition home page
Selecting Deployment > Undeploy All From This Partition for the selected partition from the Manage Partitions page

The Confirmation page appears.

If you are satisfied, click Undeploy. Note that you are warned if you are about to undeploy the last remaining revision of a deployed composite application.

Processing messages are displayed.

At this point, the undeploy operation cannot be cancelled. Undeployment continues even if the browser window is closed.

When Undeployment has completed, the SOA Infrastructure Deployed Composites page automatically displays. A confirmation message at the top of the page tells you that the composite has been successfully undeployed.

Weblogic Admin - Reset lost Password of Weblogic Server

2012-03-21T15:33:00.002+05:30

For WebLogic server, during domain creation screen you create a user weblogic (this could be any name used during domain creation screen) and set password (user and password is stored in weblogic’s embedded LDAP server in hashed format which makes it impossible to decrypt) .

What if you forgot password for this user after installation ?This post covers steps to create another user in WebLogic domain which will act as super user or create another user with same name (weblogic) with password of your choice.

Note: This process will remove all users created in weblogic’s embedded LDAP server and there will only be one user (which will act as superuser) after doing below steps.

Steps to create another superuser in weblogic (when password of existing user is lost)

1.) Open Command prompt > run . ./setDomainEnv.sh in the %DomainHome%/bin folder.

2.) In a file browser, backup %DomainHome%/security/DefaultAuthenticatorInit.ldift, then delete the file.

3.) In command prompt, go to the %DomainHome%/security/ directory, run the following command (period is important): java weblogic.security.utils.AdminAccount weblogic MyPassword .

4.) Step 3 should create a anew DefaultAuthenticatorInit.ldift

5.) Go to %Domain_Home%/servers/%server_name%/data/, delete ldap folder. (Repeat this step for all managed servers which are part of this domain.)

6.) Clear out boot.properties

7.) Verify server starts up under new password

8.) Create new boot.properties for your weblogic server(s)

9. Start (or restart) Admin Server and test if you can login to weblogic console using new username and password.

CFGFWK-64060: prerequisite missing - oracle BI-ADF runtime

2012-03-20T23:26:00.001+05:30

Detail error messages are as follow:

Issue:

while creating new domain in step select domain source I am getting "CFGFWK-64069 prerequisite missing: Oracle WSM Policy Manager 11.1.1.0 Oracle BI Composer Runtime , oracle BI-ADF runtime 11.1.1.0

Solution:

This could be because of higher security in windows vista/windows 7

Check file permission and owner of MW_HOME and subdirectory (reset permission of MW_HOME directory and subdirectory) .

If you are creating domain using command line config.cmd then start command promt in administrative mode and then try.

Fusion Middleware - Differences between Oracle and IBM

2012-03-16T15:47:00.000+05:30

Why Oracle Fusion Middleware is #1 in Middleware comparatively with IBM.

Please access below the webcasts, white papers and other resources on Oracle Fusion Middleware which are published.

http://www.oracle.com/webapps/dialogue/ns/dlgwelcome.jsp?p_ext=Y&p_dlg_id=10060238&src=7014976&Act=57

Oracle Fusion Middleware. #1 in Middleware.

SOA 11g - BPEL Tables and Dehydration store information

2012-03-13T00:45:00.001+05:30

BPEL dehydration store :

The Dehydration Store database is used to store process status data, especially for asynchronous BPEL processes.

Key BPEL tables :

Table	Contents
CUBE_INSTANCE	Stores the instance header information: domain, creation date, state (completed, running, stale, canceled), priority, title, and so on
CUBE_SCOPE	Stores the state of the instance, (variable values and so on)
AUDIT_TRAIL	Audit trail information for an instance. This information can be viewed from BPEL Console.
AUDIT_DETAILS	Large detailed audit information about a process instance
DLV_MESSAGE	Callback message metadata
DLV_MESSAGE_BIN	Payload of callback messages
INVOKE_MESSAGE	Invocation messages metadata
INVOKE_MESSAGE_BIN	Payload of invocation messages
DLV_SUBSCRIPTION	Delivery subscriptions for an instance
TASK	Tasks created for an instance (i.e. title, assignee, status, expiration)