Feed aggregator

Oracle Fights for its Share of Manufacturing - Friday, June 15, 2007 (AMR)

Chris Grillone - Tue, 2007-10-02 16:45
49% of the more than 200 respondents in these industries claim to be using Oracle for manufacturing execution, while only 36% indicate they’ve deployed SAP in this capacity.

Balance Adjustment

RameshKumar Shanmugam - Sat, 2007-09-29 16:29
When we process the payroll, there are times that the users might have deducted excess tax or other deduction, So we might need to correct the Balances for the correct YTD and the for year end reporting

There are two methods of doing it.
By defining an Balance Adjustment Element or if we know the exact amount to be corrected then we can able to adjust using the Adjust Balance Form. The latter one is very simple and it is an easy option to adjust the balance

Follow the below steps to adjust the balance using the Adjust Balance form, if we know the exact amount to be adjusted

Fast Path > Adjust Balance > Select the Assignment for which we need to adjust the balance
Set the Effective date
  • Select the element who's pay or the Input Value need to be adjusted
  • Select the Consolidation set to control the further Post-run Processing
  • Check the costing Check box if you need the balance adjustment to be costed
  • Save the work

Try this out!!!

Categories: APPS Blogs

The Battle for Relevance Rages On

Ken Pulverman - Fri, 2007-09-28 19:20
I’m following up my opening rant with some news from the front. There were two very interesting developments in the battle for your attention this week that play exactly in to what I waxed on about last week.

First of all, the offensive move. ThePudding.com made some fanfare in the news this week. Their new solution offers people the opportunity to make calls over the Internet for free if you don’t mind big brother listening in and attempting to serve you relevant ads at the same time. Early reviews are that the creep factor is more funny than creepy as a computer tries to pick out key words of wisdom from your blather and serve up ads that pertain to what you are wrapping about. I’ve signed up for the beta, so as soon as they let me in, I’ll be able to tell you more from a first hand perspective.

The interesting thing about ThePudding, is not what they are, but what they might be. They don’t plan to be a consumer-facing site in the medium term, but rather an offering for companies that provide voIP/ Internet telephony solutions. Free calls may soon be coming to Skype, Yahoo and others via a Pudding back end that enables these companies to make enough from advertising to more than cover the costs of Ma Bell’s connection charges and the thickened chocolate milk that makes it all possible. So are you willing to let a computer eavesdrop if its owner promises not to store anything you’ve said? These guys are hoping ThePudding is sweet enough to convince you to do so.

Next, the defensive move. If you tuned into NPR’s On the Media on Sunday, you were treated to a great story on Ad Block Plus, a plug in for Firefox that blocks almost all the ads you see while surfing the Internet. This one I did get to try. It works so well it is scary. Why scary? You can just imagine an advertising World War III where advertisers come up with ever more ingenious ways to serve us ads while an underground resistance figures out ways to block every new approach. The problem I foresee is that we are going to be the innocent civilians caught in the middle of this crossfire.

Ad Block Plus works by keeping a list of all of the sites that serve ads to websites and blocks those feeds, much like a virus list. Virus is an apt analogy for at least 3/4ths of the stuff I see. The folk at Internet hegemon, Google, must be seriously pissed. You buy DoubleClick for a king’s ransom as part of your attempt to sew up the entire digital marketing landscape and some joker with a .org figures out a way to block your ad feed. Sure, you can sue him to the center of the earth, but the cat is now out of the bag.

In the On the Media show, The NPR crew broached the topic of whether or not blocking ads was a form of stealing. The logic went that it costs real money to serve up these sites. If you block off their revenue source, you are essentially taking something for free – their offering – be it news, maps, reviews, or e-mail. On the surface, I agree that we do have a real problem if we bite the Internet hands that feed us. On the other hand, I’ve had to look at the same horribly annoying flashing low interest rate banner above my Yahoo e-mail inbox for the better part of a year. Yahoo must be so proud of themselves knowing that I have a mortgage. Now if they just knew when it was time for me to refinance or how unlikely I was to click on a chartreuse banner that looks like it was designed by some ex-used car salesmen. Part of me says it serves them right. Violate our trust long enough and if we are given a way to opt out, we do. Just ask the churn department at your wireless carrier.

This particular battle will be fascinating to watch. I predict détente will come in the form of permission-based marketing on sites we frequent fueled by a whole series of new companies that get much much better at behavioral targeting. Truly relevant ads? What a novel idea. It’s so novel, it’s novious.


Mary Ann Davidson - Thu, 2007-09-27 17:42

A few errata correction on my last blog entry before I go any further: 1) my mother insists that I was closer to 3, not 4 years of age when I threw a fit and demanded (and got) my own library card* and 2) the name of the devastating fire in Ketchum, Idaho last month was the Castle Rock Fire, not Castle Creek Fire. I can only plead brain fuzziness based on the amount of smoke I inhaled over the two weeks it was burning. 


Now that the fire is over, I have a newfound appreciation for the beautiful, clean, cool and pristine air in Idaho. For the two weeks the 46,000-acre Castle Rock Fire was burning, dense smoke and haze clouded the sky to the point that I could see neither the ski runs at Sun Valley (just a hoot and holler from my house) or the Boulder Mountains to the north of me. You will never know how beautiful clean air can be until you've lived through several weeks of smoke, ash, and debris falling around you. It's like living through the Apocalypse, particularly the experience of looking across the valley and seeing fire burn down the ridge so fast that it was as if it were being fanned by the Devil himself.


The fire has been hard on people, particularly businesses. It caused a cancellation of a lot of activities over Labor Day that were not only a lot of fun but that the local merchants depended on to bring in revenue. We are now officially in what is known as "slack season": hardly anybody comes here in fall, though heaven knows why. Fishing, hiking, camping and hunting are all great Idaho fall activities. I once went on a beautiful 6-mile hike to a pristine alpine lake and I did not see a single other soul during the hike, other than my hiking buddy and my dog. (Try that in California.) So come on up to Sun Valley, y'all. If there is anything better than terrific natural beauty, it's terrific natural beauty with no crowds.


My other change in perspective (besides a newfound appreciation for clean air) is the way I feel about firefighters. You hear all the time - and most of us believe it - that firefighters are heroes. I never doubted that. But it's one thing to think that in the abstract and another to have experienced it firsthand. I got to see a lot of them in Sun Valley in August, since we had 1600 firefighters in a town of 3000 people. My house was never in any real danger, for which I am grateful. Furthermore, there was no loss of life and no structural damage to anybody's houses or businesses. The critters even made out OK, too, though there are a lot of hungry bears wandering around looking for chow.  Pretty much every place in town now has a "thanks, firefighters" sign or banner displayed prominently. We really mean it: thank you, wildland firefighters, you saved our town.


Now that the fire is 100% contained, a lot of locals are saying that in the long run it is going to be healthy for the forests that we had a burn; in fact, we were overdue for one. The forest will recover; the wildlife will thrive (so long as cheat grass doesn't crowd out the sage that is a key habitat for many species). It's only been a couple of months since the Trail Creek Fire burned one of my favorite hikes in Sun Valley, but you can already see a sheen of green on the mountains and some new seedlings sprouting up through the blackened detritus. Forests recover, and a periodic burn gets rid of the underbrush that can otherwise build up and contribute to "crown fires" where the fire spreads not along the forest floor, but leaps from treetop to treetop. The difference between a disaster and a blessing in Ketchum was the skill of the firefighters, the grace of God and also the passage and perspective of time.


When you think about it, it's amazing how much of what you see really is based on your perspective. Perspective can include where you are as you look at The Big Picture, where you are in the picture and who else is in the picture.


I was reminded of this recently in a discussion with a state government struggling with open records issues. States keep a lot of data on their citizens to support, among other things, taxation (personal and property) and licensing (driver's, hunting, fishing, construction, "concealed carry"  permits and more). The question they were asking was how much of this data should be on-line and searchable?


I did not offer to write, critique or edit their state's open records laws, but I did point out to one of their legislators that a lot of concerns over privacy might depend very much on who is accessing the data and why they might want to access the data.


Most people are OK with some data being collected relevant to a transaction between parties. For example, to get a concealed carry permit in the state of Idaho, I needed to give the state some information to so they could do a background check on me. I also expect the state of Idaho to keep records about the fact they gave me a concealed carry permit (so that a law enforcement official can independently verify that I have a valid license and not a fake one, for example).


Many people who provide information for a service or transaction become unhappy if that data is accessed or sold or otherwise used for some purpose they didn't agree to. If you are dealing with a government entity like a state, you expect that when you give information to the state (that they need for things like raising taxes and providing services to citizens) they are going to use it for those "stated" purposes (no pun intended) and not for three thousand other things. I would not expect that the Idaho gun permit database would be searchable, say, by a gun ownership organization (or, conversely, by an anti-gun ownership organization). "Taint none of their goldurn business."


When data suppliers' expectations on who accesses what and for what purpose do not match with data collectors' uses, it's a problem. For example, if you've ordered books from Amazon.com, the next time you log on, you might get a friendly message that says something like, "Hi, <Your Name>! Based on your last few book purchases, we think you might be interested in the following books..." (In my case, the book list will be on military history or the Hawaiian language.) Many people might think: "Wow! How cool that they know me and can recommend books I might like!" 


Now imagine, if you will, the exact same message coming from the FBI**: "Hi, <Your Name>, based on your last five book purchases, we think you might be interested in ..." Many people would be outraged to think that the FBI (or another law enforcement entity) was looking at their book purchases. But, and here is the kicker: it is exactly the same data! Whether the above message is a "service" or an "invasion of privacy" depends on who had access to "my" data, who is doing the data analysis and why they are looking at the data. It's all about perspective.


In the private sector, these discussions take place in the realm of what a company collects, what they use the data for and who they can share the data with. Most companies have privacy policies that forbid collecting data for one stated purpose and using it or sharing it for another purpose that the "collectee" did not agree to, for example.


However, if data is public, or a public record, especially if it is Internet accessible and searchable, potentially anybody can access and analyze the data, for any purpose. My advice to the state was that they ought to hire someone to review the data they already have and figure out all the ways that data access could be misused by the evil-minded, like spear-phishers or stalkers. That is the place to start a legitimate public discussion about "open records;" specifically, how much the citizens of the state want to trade off convenience for privacy, and how much citizen data should be searchable and accessible by someone other than the state agency that collected it. It's all about perspective. 


People's perspectives on data collection can also be colored by the accuracy of the data that is kept. If someone made a mistake in doing a background check on me, that led to my being denied a carry permit, I should be able to get that "mistake" corrected. Otherwise, someone down the pike may find that I was once "denied" a carry permit and deny me something else. It's the second law of thermodynamics applied to data: entropy always increases. If data is inaccurate, inaccurate decisions will flow from use of that data.


Along those lines, there is another issue I've opined about a couple of times, and I'd be done with it except the topic keeps rearing its head in different forums, and that is the idea of "automated vulnerability testing your way to security." As much as I think that the use of automated tools can help deliver more security-worthy software and have said so, there are too many discussions of late dominated by the perspective that vendors are all evil, lazy and greedy slugs (ELGSs) that happily ship products with tons of security holes in them. The perspective of people who subscribe to the ELGS theory is that vendors must be forced to submit their code to multiple, random, unvetted tools to "validate" their security.


A differing perspective (mine) is that these tools are useful only to the extent they are used and work in development: they can't "prove" security, and vendors should license and use the tools that work well for them in development. The idea, after all, is to make products better, not have public "rat out" sessions after products have shipped. And I feel really strongly that anybody wanting to run a third party tool against a product should have to prove the tool works properly and accurately. It's only fair.


In fact, they ought to have to prove that the tool is accurate before it's used, otherwise the results may "taint" a vendor (just like a mistake in my background check could color people's perceptions of me forever if it is not corrected).


The idea of "burden of proof" is important for a couple of reasons. One of them is that we are still in the nascent stages of tool usage (if it were easy, everyone would already do it) and some of the tools don't work so well. The last thing industry needs when we are trying to promote and encourage tool usage in development is every customer, or every country, deciding that IT products need to be submitted to 348 different "tool tests."  Aside from annoyance and inefficiency, accepting tools' "vulnerability alarms" without question goes against the grain of how a lot of other things are supposed to and generally do work. For example:

  • People who are put on trial are assumed to be innocent until proven guilty. Hardly anybody gets thrown in jail for 25 years to life without someone (a prosecutor) validating the evidence, presenting it in court, and defending it (from defense challenges). The burden of proof in our court system is on the prosecution, and the standard of conviction is "beyond a reasonable doubt." (A 90% "false alarm rate" of evidence presented in a prosecution would not be "reasonable doubt.")

  • Journalists are expected to check facts before reporting that, for example, a celebrity was caught in a love nest with another celebrity. Furthermore, if journalists get the news wrong, they generally print a retraction or correction. (Of course, at that point, reputational damage may not be "retractable," which is one reason why good journalists are rigorous about fact checking.)

  • Gossip is called "gossip" and not "impartial fact exchange" because so much of it is not true and potentially hurtful or damaging. This is why your mom tells you not to do it. Mom is right, as she almost always is.


The ugly issue in the promise of automated vulnerability tools is that there is no standard for these tools: what they find, how well they find it. Which means anybody can create a tool, point it at a product, claim to find problems, and all the work is on the product vendor to prove their product does not have a problem instead of on a tools vendor to prove the tool is accurate. And let me tell you, having to go through hundreds or thousands of "potential vulnerability fire alarms"  to validate every one makes security worse, not better, because it takes a scarce resource (a security-aware developer) and puts him/her to work chasing phantoms instead of improving products.


Some tools vendors push the "evil vendor" perspective because to the extent they can convince IT vendors' customers that their products need to be scanned, they create fear, uncertainty, and doubt (FUD) and thus increase the demand for their scanning product. Can't blame them for that: it's capitalism at work. That said, I take the perspective that these tools offer promise, but they need to be validated to prove that they are accurate before anyone can be expected to use them. Only if they are accurate are they useful. If they are inaccurate, they are useless and harmful.  (Putting it differently, if IT vendors need to "prove" their products are secure, why shouldn't tools vendors need to "prove" their tools are accurate before anybody would even think of using them? What's sauce for the goose is sauce for the gander.)


Lastly, some of these tools are so "chattery" and "noisy" that it really is like gossip and, like gossip, the damage is done even if there is a retraction. A tool that has a lot of false alarms taints a vendor's brand just like tabloid journalists can print innuendo that damages someone's reputation unjustly. I shouldn't have to prove the coding equivalent of "I did not spend the weekend in a love nest with a celebrity,"  the vulnerability tool maker should have to prove that I did.


(Aside: one of my own amazingly wonderful ethical hacking team members just improved one of our internally-developed tools, a protocol fuzzer lovingly called BitRotter, to do more pernicious and nefarious code breaking in a good cause. He's just rechristened it ByteRotter. Thanks, Jeff.)


Clearly, my perspective isn't unbiased, because I work for an IT vendor. I believe in better security, doing more in secure development, and in industry "raising the bar" through better development practice. Automation (and automated tools) can definitely help.


I also believe in accuracy and fairness as basic principles of any business undertaking, because it is only when the haze and smoke and debris is swept away, that you can see - really see - what is there.


I climbed to the top of the ridge behind my house a few days after the Castle Rock Fire was declared 100% contained. The fall rains had come to help soothe the burns, and the winds that a few days prior had been fanning the fire were now whisking the few remaining puffs of smoke out of the valley. It's about a 600 foot climb through sage and scrub, but when I got to the top of the ridge, I could see the Boulder Mountains in the distance, and the ski runs at Sun Valley, still green and beautiful, and the aspens beginning to change color on the mountains that ring the Wood River Valley.


After two weeks of hellish smoke and ash and debris, I could see rightly - 'ike pono, as the Hawaiians say - for miles and miles and miles. There is no better perspective than that.



*  Mom also noted it was far from the last fit I would throw. What can I say? I learned useful business skills early.


** Disclaimer: I know several people who work for the FBI. They have difficult jobs that the rest of us don't understand and take for granted. I am quite sure they have more important things to do than check up on my latest book-buying binge. Ergo, no slight to them was intended nor should be inferred.


For more information:


Book of the week: I just read another book by James Hornfischer: Ship of Ghosts, about the USS Houston, sunk at the Battle of Sunda Straights in March 1942. Many of the survivors were forced to build the Burma Railway. An amazing story of survival and heroism. Definitely worth a read.




About the Castle Rock Fire:





Transition period

Fadi Hasweh - Wed, 2007-09-26 04:46
Dear all,

I would like to inform you that I am currently at a transition period i moved to a new country and I am trying to explore my options there and that’s why I am not able to post/reply at forums and email list, but every thing will be back to normal within a month.
Wish me luck

What do you want to learn about?

Anthony Rayner - Mon, 2007-09-24 07:14
In the interest of trying to write good posts that the APEX community will find useful, I have added a new 'poll' feature to my blog. My first poll is entitled simply, 'What would you like to read more about on my blog?' and I have suggested a few titles to pick from. You can cast your vote by selecting from the check boxes on the right of the page, below 'About Me'.

If you have any other suggestions or areas you wish to learn about or understand better, then please add a comment to this post.

Look forward to hearing from you!

Categories: Development

India wins world cup

Siva Doe - Mon, 2007-09-24 05:24

This is cricket Twenty20 world cup. The final was against arch rivals Pakistan. This cant get any better. The last time these two teams met ended in a 'tie' and India won through a novel way of tie-breaker called 'bowl out'. The final too threatened to go the same way with India taking the last wicket in the last over of the match.

Well done India. Well done Dhoni, the new captain and all players. You made my day and week.

Constructing Java Objects with Thread-safety, Reusability and Encapsulation in Mind

Menon - Sun, 2007-09-23 17:31
After a long hiatus (during which I gained a new-found respect for the prolific bloggers who post daily), I am finally back with my first article titled Constructing Java Objects with Thread-safety, Reusability and Encapsulation in Mind. Please provide your feedback in comments. Hope you find the article useful.
PS: I could not post the article directly in the blog since it messed up the code formatting. Hence I posted it on my web site.

Using Dynamic Sql to work around PL/SQL bugs

Mike Moore - Sat, 2007-09-22 17:26

A coworker encountered this problem. We search the Internet for a solution, but nothing was found. I am hoping that by posting this, others having the same problem will quickly find a solution. Furthermore, this example illustrates a more general principle which is that sometimes things work in SQL which do not work in PL/SQL and a simple solution is to use dynamic sql.

This problem is encountered when trying to access an NVARCHAR2 using a TABLE function in PL/SQL.

ORA-12714: invalid national character set specified

Originally written as:

FOR c IN ( SELECT * FROM TABLE (p_question_tab_i) ) LOOP



Raises error: ORA-12714: invalid national character set specified

Then re-written using dynamic SQL:

OPEN que_cursor FOR 'SELECT * FROM TABLE (:question_tab)'

USING p_question_tab_i;

The above example works correctly…



Technically, this is not a PL/SQL bug. It is, however, a feature that is supported in SQL but not PL/SQL. This often happens with new SQL features where PL/SQL has not 'caught up' yet.

Know New Marketing - What in the H are you talking about?

Ken Pulverman - Fri, 2007-09-21 12:52
.....yes it's a play on words....I'm fond of those, and if we ever meet in person, or perhaps even in this blog, you'll have to endure some bad puns as well.

So what am I getting at? Well a growing number of us believe that marketing, as we currently know it, is dead. As consumers we are tired of the window dressing, snake oil, and spin. Tell us what is is, what is does, and why I should care. ...and make it quick, because I have an inbox full of spam like you wouldn't believe, or maybe you would.

Why did it die? Simple. Trust. What was that our scholar of a president tried to reiterate - Fool me once, shame on you. Fool me twice...and that is where he lost it, but you know what comes next.

Collectively we are sick of the junk mail, the valueless untargeted commercials, the mailbox full of crap. In our limited time on this rock, we search for meaning and purpose and there are a whole bunch of direct marketers who want to waste that precious time. We trusted you, and you burned us one too many times. Like many folks, I've moved to triage mode on the tons of messages trying to reach me. If I can figure out what it is with reasonable certainty it gets deleted or thrown out without ever being opened. I am currently looking for a shredder big enough to accept those 20 page credit card offers poorly masquerading as important courier envelopes, unopened of course.

So as you can imagine, it produces a fair bit of cognitive dissonance for me to work as a marketer. Fortunately there are a growing number of us hell bent on leveraging new marketing techniques to prove the substantial ROI of marketing.

With the democratization of all of the media channels, marketing today is about conversations. Broadcasts and monologues are so yesteryear. This blog will explore how to reach your customers, members, constituents post Marketing 1.0 through the conversations that matter to them (and guess what, its almost never going to happen on your website).

So buckle up, java down and join me in this dialogue where we will chart the course for where we go from here. The good news is that the only way is up.

The big news for Canada

Peter Khos - Fri, 2007-09-21 11:33
Most of the news last week in Canada has been on the fact that the Canadian dollar is almost at par with the US dollar. The last time that it was at par was in 1976 (more than 30 years ago). What is so special about it? Well, depending on which perspective you are coming from, there are ramifications. For example, as a consumer there are savings to be had depending on what products are being Peter Khttp://www.blogger.com/profile/14068944101291927006noreply@blogger.com2

OC4J ping timeout issues

Vidya Bala - Thu, 2007-09-20 16:43
We recently went with a Jdev Application using Oacle Application Server 10.1.3. While the deployment went fine, a few days after the deployment we started noticing oc4j ping timeout issues in the opmn.log. After the OC4J ping timeout OC4J tries to restart itself. We checked the max heap size - the max heap size looks good. There is not much activity on the server so we feel the default ping timeout of 20 seconds should be sufficient. I don't believe it can be a JDK version issue either - since out dev/test environment does not have this issue and is on the same version. will be great to know if anybody has run into a similar issue and know of any possible solutions.
Categories: Development

Oracle 11g New Features DBMS_ADDM for RAC

Virag Sharma - Thu, 2007-09-20 08:37
Virag Sharma virag123@gmail.com

In OCP Oracle Database 10g Exam Guidechapter 3 “Automatic Database Management” there is question

5. To retrieve the ADDM reports using SQL, what do you need to do?

A. Run the addmrpt.sql SQL script
B. Use the DBA_ADDM view
C. Use the DBA_ADVISOR view
D. Use the DBMS_ADDM package

Answer “A” is correct and D is wrong because there is no PL/SQL package named DBMS_ADDM.
But in 11g , it is not true , i.e. Package DBMS_ADDM is there in 11g. In case of RAC script
run give report for single instance, not report of all instance in RAC. But using DBMS_ADDM , we can generate report for all instance of RAC.

Different mode of DBMS_ADDM

  1. Database Mode Instance Mode
  2. Partial Mode

Database Mode of DBMS_ADDM

In database mode DBMS_ADDM , analyze all instance in RAC

VAR tname VARCHAR2(30);
VAR start_snap_id number;
VAR end_snap_id number;


:tname := 'DB_MODE_TEST_RAG';
:start_snap_id := 100 ;
:end_snap_id := 200 ;
DBMS_ADDM.ANALYZE_DB(:tname, :start_snap_id, :end_snap_id);


Instance Mode of DBMS_ADDM
In Instance mode DBMS_ADDM , analyze one particular instance

VAR tname VARCHAR2(30);
VAR start_snap_id number;
VAR end_snap_id number;
VAR INST_NUM number;
:tname := 'INST_MODE_TEST_RAG';
:start_snap_id := 100 ;
:end_snap_id := 200 ;
:INST_NUM := 2;
DBMS_ADDM.ANALYZE_INST(:tname,:start_snap_id,:end_snap_id, :INST_NUM );


Partial mode of DBMS_ADDM

In partial mode DBMS_ADDM analyze subset of instances. for example we want to analyze instance 2 and 4 out of four node RAC

VAR tname VARCHAR2(30);
VAR start_snap_id number;
VAR end_snap_id number;


:tname := 'PART_MODE_TEST_RAG';
:start_snap_id :=100;
:end_snap_id := 200;
DBMS_ADDM.ANALYZE_PARTIAL(:tname,'2,4', :start_snap_id, :end_snap_id);



Displaying an ADDM Report
  SET LONG 1000000 PAGESIZE 0;



Categories: DBA Blogs

SOA on grid

Rakesh Saha - Thu, 2007-09-20 01:17

INI Madness Tamed!

Mark Vakoc - Wed, 2007-09-19 22:52
As many might be aware the task of managing the INI files, used to store the configuration of our server based products, can be difficult at best. Server Manager addresses many of these problems in the following ways:

Complete INIs:
Server Manager provides a web based tools release specific mechanism for editing the configuration files of our server based products. Using Server Manager there should be no reason to manually edit the INI files directly. Server Manager provides a web based view/editing of all the configuration files.

Server Manager utilizes metadata about configuration settings that are delivered with each tools release. To accomplish this we performed many searches over the entire codebase to find every configuration item used. Our policy is: if something is configurable via INI it is configurable via Server Manager. This search resulted in the addition of many, some possibly obscure, configuration settings. It also resulted in the removal of many configuration items that have historically been delivered but are no longer relevant.

For existing enterprise servers that are registered with SM many configuration settings that were present in the JDE.INI that are no longer used will remain in the file, if present, but won't appear using the Server Manager GUI. For our web based servers the INIs are created when the instance is created, so will perfectly match the tools release initially used. If a setting is present in these web based INIs and the server is later upgraded to a release that obsoletes a setting that parameter will still remain in the file, but will no longer be viewable through the management console.

It is, of course, possible that we missed a setting. We did our best, but there are a lot of settings to manage. If a setting was missed and is therefore not available through the management console application it may always be edited directly within the file. All settings not known to SM will be maintained during tools release upgrades/downgrades.

Each configuration item is identified using a short, human readable description. An extended description is provided via the online help and bundled documentation. Default values, where applicable, are provided as reference. Many parameters provide a list of values detailing exactly what is allowed for each setting. For reference the documentation provides the INI filename, section, and entry for each setting.

We've also provided a reference document with the product detailing each setting. As of this writing this is over 350 pages. All the information in the documentation is also available in online help. If you are looking for a particular setting and are having trouble locating it using the new descriptions the documentation allows a quick lookup based on the INI entry details.

This reference documentation is current as of the 8.97 tools release. It will be kept current for all future tools releases. The reference may also be of assistance to earlier tools release but be aware that not all settings will be applicable to the earlier releases.

Relevant INIs:
Another task we undertook was to remove the configuration parameters that are not relevant to the product. Historically the JAS.INI and JDBJ.INI used for web servers were simply duplicated for the other web based products (collaborative portal, transaction server, PIMSync server, and the new business services server). We evaluated these products and removed from their configuration parameters that didn't apply. This means that each server has it's own unique set of configuration parameters. We hope this will reduce confusion in not appearing to require configuring parameters that do not apply to the server.

The transaction server (RTE) also previously contained three separate copies of each configuration file, one for each of the EARs that make up the product. This has been removed and only a single set of configuration files are shared among all the EARs.

There's much more to talk about configuration management in Server Manager: server groups, configuration comparison, and audit history. I hope to post on those topics in the future.

Quick History of Me

Mark Vakoc - Wed, 2007-09-19 22:24
Here's a quick background of who I am, why I'm blogging, and what I hope to accomplish here.

I have been with JD Edwards/PeopleSoft/Oracle for almost ten years now. The first three or so years were spent on the support organizations SWAT team flying to customer sites to address specific customer issues and provide technical assistance. Life on the road was great; I traveled to more than twelve countries and countless client sites and really enjoyed the work. It came time to stop traveling so much so I settled down in the Denver area and created the Support Assistant diagnostic product. I'm still very proud of SA, and am glad to say that the product is alive and kicking. More on that later.

After working primarily on SA for five or so years I decided to tip my hat into something new. I wanted to apply my experience from the field and support organizations and create something new. The result is Server Manager. Specifically, I wanted to address
  • The difficulty in installing and upgrading our server based products
  • The difficulties around configuration management; understanding all the configuration parameters and managing the configuration of servers across an E1 installation
  • The difficulty in monitoring the activity of E1 servers
  • The difficulty associated with troubleshooting servers when something goes wrong
Hopefully you'll see that Server Manager addresses these and many other administration activities that will truly result in a lower cost of ownership.

As someone unbelievably addicted to blogs, generally of a geeky nature, I've been "inspired" by many others to use this forum to publish tips, tricks, knowledge, and general musings on the product of which I'm so proud. I'm particularly inspired by a blog by a co-worker entitled 'The Buttso Blathers' with very insightful posts on all things OAS (Oracle Application Server).

There is one thing this blog does not represent; it is not a support forum or a place to seek help.  So tune in and learn more about the exciting Server Manager product.


Mark Vakoc - Wed, 2007-09-19 22:19
Before digging into the product itself I want to express some thanks to the team that worked on Server Manager. At this point I'll let the involved parties remain anonymous. This was a team effort, and I want to express my personal thanks to the development team and quality assurance team that helped create the product.

So, for all those involved in Server Manager, I say thanks.

Making Sense of Fusion Middleware

Solution Beacon - Wed, 2007-09-19 18:22
The Fusion Middleware area has become more and more crowded with all of the products that are now included.I speak from personal experience on this topic since I'm often stumbling through the various acronyms used for these products.Most of us think that Fusion Middleware refers to Service-Oriented Architecture, Identity Management and Business Process Management since these are usually the

Redwood Shores

Fairlie Rego - Mon, 2007-09-17 15:02

I was in Redwood last week and got a chance to meet some of the best minds in Server Technologies including a few ex-colleagues and a couple of guys on the revered
Oak Table

And although a significant part of the week was spent in the wine and lounge bars of San Francisco it was quite an enriching experience..

Inside the Middle

Solution Beacon - Mon, 2007-09-17 12:44
I've written generally about Oracle Fusion Middleware but let's move down to the next level of detail. An easy way to do this is to focus on functionality. There are seven functional categories of products in Fusion Middleware, per Oracle.The Unified Workplace group which provides collaboration tools (Groupware, Instant Messaging), portals, mobile/desktop presentation and secure search.The


Subscribe to Oracle FAQ aggregator