Portal Implementation : White Paper

Hello Guyz,
I am implementing ESS and Portal for the First time & facing lotz of issues and keep solving the same.
After finishing with this implementation (soon), i am planning to publish White Paper with regards to all the issues i have faced.
I need idea about the white paper: i mean, what all should i include in white paper and also i would be greatful if any one shares the template for White Paper
Regards
Vijay

Vijay,
Check out the sdn
https://www.sdn.sap.com/irj/sdn/submitcontent
Right side you can see the SDN template for all Contributors.
I shall share you later on what are all the topics need to be covered.
Regards,
Karthick Eswaran

Similar Messages

Developing JSF Portlets with WebLogic Portal (Oracle White paper May 2009)

I have created a simple JSF Portlet following the steps delineated in paragraph 3.1.1 Creating a JSF Enabled WLP Web Project of the white paper mentioned above. I used Workshop for Weblogic 10gR3. When I tried to deploy that very simple portlet and portal I got this error message :
"!MESSAGE Unable to register J2EE shared library C:\bea\wlportal_10.3\samples\lib\j2ee-modules\wlp-sample-lookandfeel-web-lib.war".
Clearly the folder and file "samples\lib\j2ee-modules\wlp-sample-lookandfeel-web-lib.war" are not under my "C:\bea\wlportal_10.3". My question is where do I download it? Where does it come from?
Thanks in advance.

Maybe you did not include the samples when you installed Oracle WebLogic Portal? Now that this is an Oracle product, samples are not installed or configured by default. This is a change in policy from when WebLogic Portal was a BEA thing, so it takes some getting used to and there are probably plenty of places where documentation and papers could be enhanced to emphasize this.
In addition, it looks like there might be an error in the white paper with respect to configuring your web app to include samples. I don't see any mention of taking an extra step to include the sample facets in your portal app. This oversight may have been caused by the author working with a pre-release of Oracle WebLogic Portal that had not yet been "Oracle-ized" enough to get the default samples out of there. In the old days, I think the samples were automatically included in your portal web app.
To get the samples in a new portal web app while you are creating it with the IDE you can click the "Modify..." button on the first dialog. It is next to the "Configuration" text area. This pops up a dialog that lets you select the "Weblogic Portal Samples" facet for your web app.
To get the samples in an existing portal web app after it has been created, right click the app in the IDE, click "Properties...", click "Project Facets", and select the "Weblogic Portal Samples".
Sorry, I'm not sure what the remedy is for getting samples into an installed product that was not installed with the samples. Unfortunately, I think that is the problem that you need solved. Sorry about that. Hopefully you are working in a test or dev environment that makes it easy to blow away old installations and start over? If not, then maybe install it with samples someplace else and copy the samples/... dir over to your other install?

Express White Paper

Thanks to all those who responded requesting the Express white paper. I
received an overwhelming response. I was expecting a dozen or so
requests - I received over 80. Apparently there is strong demand for
lessons learned about working with Express.
The paper is in-progress. Everyone that requested it will get it when
it is ready, hopefully before end of September. BTW, my paper on
Express and the Object/Relational Problem will be published by Dr.
Dobb's Journal about that time also - the publisher tells me that the
November issue will be on the newsstands by end of September. The DDJ
article is a review of the basics of Express, what it does, and how
you develop with it. It also includes our early experiences with it
(article was written end of April and reflects almost three month's
experience with Express at that time). The article also goes briefly
over our concept for a rapid process specific to Express. The white
paper will have much more to say on the topic.
Several people thanked me for my generosity in offering a free white
paper and sharing our experiences with the Forte' community. There is
nothing generous about the offer: it is unabashed self-promotion in the
finest tradition of American crass commercialism. We're a consulting
company. We sell our knowledge and experience. If, after you get the
white paper, you would like to retain us on a consulting assignment we
would be very grateful, and you will have a chance to pay us back for
our generosity. If not, maybe you can reciprocate and share your
experiences.
Now to the subject of this posting: why am I posting this now? Well,
for one thing, I received several responses that said something
like: " we've tried Express and we were disappointed with ...", or "we've
been using it and have been frustrated with ...", or "we've evaluated it
and we had difficulties with ...". I started writing reply notes to each
of the individuals who expressed those negative experiences, but when I
reviewed what I wrote, it sounded like a Dear Abby column, with the replies
sounding like: Dear Disappointed, or Dear Frustrated, or Dear With
Difficulties. I decided I'll just post one note for all those who've
had negative experiences, or who are just starting to use/evaluate Express
and are likely to have similar experiences. Hence this. I also felt that
I should give people somewhat of an overview of what's coming in the
white paper while they're waiting to get the finished product.
Perhaps initial difficulties with Express is a problem of unrealistic
expectations. I always try to remember Mick Jagger's words. Mick, as
everyone knows, is one of the great software minds of the 20th century:
"You can't always get what you want ...". You must determine if you're
getting what you need.
Seriously, I have been working on the object/relational "impedance
mismatch problem" for close to ten years now (since 1987 when I
developed an Ada/SQL binding for the US Department of Defense). I have seen
many solutions, and have developed several myself for C,C++,Ada and
for Oracle, Sybase, Informix, and Ingress. I find Express to be one
of the most elegant solutions to that thorny problem. If you look at it from
that point of view alone, it's very hard to fail to be impressed. If you're
expecting Express (or PowerBuilder 5, or any other solution) to be yet another
Silver bullet to slay the development monster then you'll be disappointed.
Software development is hard, will continue to be hard, and will continue
to get more complex. Anything that can help us eliminate or reduce what
Frederick Brooks calls "accidental complexity", and design around "essential
complexity", will help. Forte' and Express definitely do that. Paul
Butterworth's paper on "Managing the New Complexities of Application
Development", shows how Forte' has solved many of the development/deployment
problems. If you haven't read it, I highly recommend it. If you have, I would
recommend a re-read if you've forgotten why you chose Forte' to begin with, or
if you yourself did not participate in making that choice, The Express user's
manual, "Using Forte' Express", shows how Express extends Forte' to reduce
the complexity of developing RDBMS-based systems.
To get an appreciation for what Express does for you, try a simple
experiment : spec out a GUI/RDBMS application, say the order entry application
that comes with Express as a tutorial. Do it without Express. Then do it with
Express. Try to make the application as complete as possible - it must
implement all your business rules and have all the behaviors that you desire.
Relax a bit about look and feel. Also Remember to keep the experiment fair.
As part of your application development come up with a framework and an
architecture that the next application will use. Your non-Express application
also must be as extensible and modifiable as Express allows an Express
project. Record the development time of both. If you can beat Express in
development time, then you're a Forte' development Guru and people should be
beating a path to your door.
Lest anyone think I am a cheerleader for Express, I want to mention that
I have some very strong disagreements with several aspects of the
Express architecture. One major problem I find with it is conceptual.
The Express relational encapsulation has added a great deal of accidental
complexity, i.e complexity that is not inherently there because
of the nature of the problem. It arises because of design or implementation
choices. Express represents each database table with three classes (there is
actually six classes per table, three of which are just derived place holders
to contain customizations, so we'll ignore them for this discussion). For a
table EMP, Express produces three base classes: an EMPClass, an EMPQuery
class, and EMPMgr class. The EMPClass is quite understandable. It
encapsulates the table's data. The EMPMgr class is somewhat understandable,
it encapsulates operations that manage the table's data as it crosses the
interfaces. But why do we need one class per table? A manager should manage
several things, not one thing. That leads us to EMPQuery, the encapsulation
that I have most difficulty with: creating a query class for each table. That
is definitely the wrong abstraction.
If you consider that, in general, a SQL query is multi-table:
select t1.col1, t2.col2, t3.col3, ...
from t1, t2, t3, ..
where <expressions on t1.col1, t2.col2, ...>
order by <expressions on t1.col1, t2.col2, ...>
you'll see that the abstraction here is a query tree across many tables,
many columns, and a large variety of expressions - single and multi-table. To
attempt to encapsulate that in objects that are basically single table objects
will produce a great deal of accidental complexity. The design choice of one
query class per table makes writing one-table queries simple, but writing
multi-table queries awkward.
The Express architecture would be much simpler if there is a QueryTree
class for all tables. Better yet, leave the representation of queries as
text strings - ANSI or Forte' SQL on the client side, and DBMS-specific on the
server side. A great deal of complexity in doing query customizations will
be reduced. You will lose some type checking that the current design has, but
hey, you can't always get what you want. When you have several hundred tables
in your database and Express generates six classes to per table, you'll see
that the number of classes generated as excessive. When you try to design a
general query modification scheme you'll realize how awkward multi-table joins
are to do via the Express BusinessQuery class. Last week I was developing a
general design for row-level security, the query structure drove me crazy,
I ended up catching the generated SQLText and inserting the security
constraints.
Now back to the Dear Abby column: If you're unhappy because of performance
issues, try to isolate the reason for the poor performance. This is not easy
in 3-tier applications. Don't be too quick to blame the bad performance on
Express. Do you have a non-Express benchmark application that does the
same thing and outperforms Express? Don't be too quick to blame Forte'
either. Do you have a non-Forte' benchmark, that does the same things
and outperforms Forte'? The operative words here are "does the same
things". A VB application that issues a SQL Select is not a benchmark.
Forte' allows you to instrument applications to study performance
bottlenecks. Find out where your hot spots are and try to do some design
work. If the Express architecture gets in the way, it's time for feedback
to Express developers.
Performance issues, particularly in 3-tier client/server systems are
multi-faceted and complex. There are many interactions of database
issues, interaction of the database with TOOL language issues, locking,
caching, timing of asynchronous events, shared objects, distributed objects,
remote references, memory allocation/deallocation, message traffic,
copying across partitions, etc. etc. that have to be considered. There
was an interesting discussion just a few days ago on multi-threading
on the client side, and blocking in DBMS APIs. Issues like that can
keep you bogged down for days. I have worked on several performance efforts
on triage tuning teams and swat re-design teams, where several hundred man
hours were dedicated to performance and tuning of c/s systems. Big and
complex topic. What I would advice about performance is what Tom Gilb says:
"(1) don't worry about it, and (2) don't worry about it yet" - assuming of
course that you have a rational design, and a sound framework. Many sins of
design are committed in the name of performance. Anyway, enough
of the harangue about premature considerations of performance. Bottom
line is : once you get your functionality, instrument, measure, and tune. If
your architecture was sound, you won't have to re-design for performance, you
would've designed it in.
On our project the system is so large we are subsumed with rapid process
issues: how can we get this monster finished on time? without having to
expand the team to several times its size, and without having to spend more
than we can afford? The upcoming white paper's focus will be on the rapid
process. Probably at a later date, we'll do another paper on performance
issues with Express.
Another reason you may be unhappy with Express is if you perceive that
it is the wrong tool for your application - but was chosen by
corporate mandate. If your application does not involve an RDBMS (say
real-time process control), then Express is obviously not for you. It may
also appear that Express is not suitable for your application if your usage
of the RDBMS is marginal, but your application logic is quite complex (in our
case the application has many AI aspects to it, a rules-based database, and
many interconnected patterns of rules, and rich behaviors). If you find
you're spending too much time doing things outside Express, fighting
Express, or doing way too many customizations, then Express may
not have been the right choice for your application.
Don't think, however, that Express is only for those applications that
maintain relational base tables. You can use a relational database to
store tables other than base tables (state transition tables, dialog
support tables, views, and other kinds of virtual tables). To make use
of Express's powerful application generating capabilities you can use
tables created for the sole purpose of of supporting an Express
application model. The table is in essence, a state transition
diagram. The Express application model creates rows in this
virtual table while the dialog is in-progress. You can use insert and
update triggers in your SQL engine to do the real thing to your base
tables. This trick is among some I'll detail in the white paper.
Another reason some people may be unhappy with Express may be methodology
tension between those who use behavior-driven methodologies (Booch, Jacobson,
Wirfs-Brock), and those who favor data-driven methodologies (OMT, Coad). If
you're in the first camp, you'll probably feel that the modeling done via
Express is not adequate. You'd probably say "that's not an object model!
that's an ERD". You would be half right - the Express business model shows
only containment and association relationships. It does not document "uses"
relationships, so it really can't be considered a full object-model. Granted;
but once you make that realization, your reaction should be one of joy, not
sadness. This is a brilliant reduction in the amount of modeling that needs
to be done since most MIS systems are dominated by their data-model, not their
behavior model (See Arthur Riel's Design Heuristics) . Behavior-based methodologies,
with their documentation of use-cases and class behavior will tend to be analysis
overkill for most MIS projects. For some OOA/OOD practitioners, going back to a
data-centered process may be unpalatable. For those folks my advice would be to try to
look at the business model/application models as meta-models. Take the
generated classes and produce a full object model if you wish. Document your
domain classes in your favorite CASE tool. By all means document
domain-pertinent behavior and use-cases, they will help you test. But do
appreciate the productivity gain produced by the reduction of modeling load
that Express data-centered approach gives you. Your detailed
behavior-based, use-case model may be a luxury you can't afford.
If the methodology clash manifests itself politically in your
organization, where you have the OO purists pooh-pooh a data centered
approach, then you have my sympathies. My best advice is to cool it on the
methodology religion front. If you have a product to deliver, you can't
afford it. Also keep in mind that even if your modeling work is reduced by
adopting a data-centered Express process, you'll still have ample
opportunities to fully utilize your OOD expertise when it comes time to add
functionality or improve performance of the entire application as a whole.
There will still be processes where Express may not be expressive enough. Those
processes whose behavior is so rich and intricate that you cannot find a
data-based trick to model them with, you'd have to do outside Express. These
should be rare and the exception not the rule in MIS systems, however.
Does that exhaust the list of reasons of why people may be
disappointed in Express? Probably not. Undoubtedly Express reduces your
degrees of freedom, and constrains your choices, but many times "jail
liberates". More reasons? I've heard some complaints about repository
corruption problems. I'm not aware that we've had those, or that it is
something due to Express. I'll check with our Forte' system manager. If we
have, they must not have been show stoppers, and our system manager must
have dealt with them quickly enough that the developers did not notice much.
Until you get the full paper in a few weeks, I'll leave you with some
thoughts about Express, and OO development in general:
1. Learn about the concept of "Good enough" in software
engineering. Here are some sources:
- Ed Yourdon: Read Ed Yourdon's article in the last issue of Byte,
titled "When Good Enough is Best". One of Yourdon's tips in the
article: "It's the Process, Stupid!"
Don't take "good enough" to mean that development with Express
requires you to lower your expectations, or lower your
standards. You must tune the concept of "good enough" to your
acceptable standards.
- Arthur Riel: Read Arthur Riel's great book "Object-Oriented Design
Heuristics". Riel shows that there are many problems with no optimal
solutions. This is particularly true in those systems that
are not purely object oriented. Systems that interface with
non-object oriented "legacy" systems, which is what Express
is. Also, Riel's discussion of behavior-based vs data-based
methodologies is very illuminating.
2. Don't obsess about look and feel. That's where Express is most
constraining. If you have unique look and feel requirements,
and look and feel is paramount to you, save yourself some pain and
choose another tool, or sing along with Mick: you can't always get
you want ...
3. Be clear about what rapid development really means. An excellent
resource is the book by Steve McConnell of Microsoft: "Rapid
Development - Taming Wild Software Schedules". A thick book, but the
chapters on best practices, and the tens of case studies are great. The
book shows clearly the differences between evolutionary
delivery, and staged delivery. It shows the differences between
evolutionary prototyping, throwaway prototyping, user-interface
prototyping, and demonstration prototyping and the appropriate uses
and risks of each. In our white paper we advocate a life cycle
approach that is basically evolutionary prototyping, with evolutionary
delivery, and occasional use of throwaway prototypes. We don't advocate
using Express for demonstration prototyping.
4. Realize that Express is maturing along with the product you're
developing. If you don't have deep philosophicalobjections to the
Express framework and architecture, then most of
the concerns with Express would be temporary details that will be
smoothed as Express, and Forte', mature. How long did we wait for
Windows to mature? Let's be fair to the Express developers.
5. The main keys to success in Express are not rocket science (I
worry now about having hyped up people's expectations myself). The
major keys to success revolve around management issues, not
technical issues: expectations management, process management,
and customizations management.
The full paper includes the design and implementation of a Customizations
Management System that allows you to plan customizations needed and to
inventory customizations completed. It automates the process of
extracting the customizations completed from the repository and stores
them in a relational database. A customizations browser then allows
management to plan and prioritize the implementation of customizations. It
allows developers to study the completed customizations and to reuse code,
design, or concepts to implement further customizations. Managing
customizations is absolutely essential for success in Express. The paper
will also detail a rapid process that is "Express friendly".
I'm glad there was such a big response to the white paper offer. Now I have
to sit down and write it!
Nabil Hijazi Optimum Solutions, Inc.
[email protected] 201 Elden Street
Phone: (703) 435-3530 #501
Fax: (703) 435-9212 Herndon, Va 22070
================================================
You can't always get what you want.
But if you try sometime, you might find,
you get what you need. Mick Jagger.
------------------------------------------------

[email protected] wrote:
>
A few comments on Nabil Hijazi's observations...
Nabil Hijazi writes...
One major problem I find with it is conceptual.The Express relational
encapsulation has added a great deal of accidental complexity, i.e complexity
that is not inherently there because of the nature of the problem. It arises
because of design or implementation choices.
Paul Krinsky comments...
Anyone who has used NeXT's Enterprise Object Framework (EOF) will be at home
with Express's architecture, it is very similar. NeXT has been around for a
while and have gone through a lot. They originally started with DBKit to solve
the persistence problem. Basically it wrappered the database libraries. EOF was
created when it became clear that the DBKit approach wouldn't work. EOF has
EO's (Enterprise Objects), EOQuery, EOController, etc. that do pretty much what
BusinessClass, BusinessQuery and BusinessMgr do. I'm not sure if Forte hired
people with NeXT experience, but it would be interesting to find out if both
companies came up with the same architecture independently. What are the
chances?
Nabil Hijazi writes...
The design choice of one query class per table makes writing one-table queries
simple, but writing multi-table queries awkward.
Paul Krinsky comments...
I don't think BusinessQuery is too bad once you get used to it. Multi-table
queries are pretty easy if you use the foreign attributes Express provides to
build connected queries. One feature I miss from EOF is the EOFault. An EOFault
stands in for an object to reduce the overhead of retrieving everything an
object has a pointer to. For example, a retrieve on customer that contains an
array of orders would bring in EOFaults to stand in for the orders. When one of
the orders was referenced, EOF would produce a fault (hence the name) and go
and get the required record. Of course you could force EOF to bring the real
data and not use EOfaults if you wanted (if chance were high that you would
need it). This feature saved a lot of memory and increased the speed of
retrieval while still providing transparent access from the viewpoint of the
developer. Another cool feature was uniquing. EOF kept track of the EOs it
retrieved for a client. So if two windows both retrieved Customer X, EOF would
realize this and point the 2nd window at the copy already in memory. This
avoided having multiple copies of the same object in memory and allowed
provided everyone with the most current changes.
Nabil Hijazi writes...
The Express architecture would be much simpler if there is a QueryTree
class for all tables. Better yet, leave the representation of queries as text
strings - ANSI or Forte' SQL on the client side, and DBMS-specific on the
server side. A great deal of complexity in doing query customizations will be
reduced. You will lose some type checking that the current design has, but hey,
you can't always get what you want. When you have several hundred tables in
your database and Express generates six classes to per table, you'll see that
the number of classes generated as excessive. When you try to design a general
query modification scheme you'll realize how awkward multi-table joins are to
do via the Express BusinessQuery class. Last week I was developing a general
design for row-level security, the query structure drove me crazy, I ended up
catching the generated SQLText and inserting the security constraints.
Paul Krinsky comments...
I like the fact that Express manages the mapping to the database. I can change
the underlying database schema and all my queries still work. When the DBAs
inform me that I'm not following their naming standard (remove all vowels
except for 207 "standard" abbreviations that somehow got blessed then compress
to 8 characters using a bit compression algorithm that NASA would be proud of -
am I ranting?) it lets me conform without having to deal with it except in the
business model. It's nice to have a layer of abstraction.
I'm not a big fan of having all the generated classes either. I think it's a
necessary evil because of TOOL. NeXT uses Objective-C which is much more
dynamic in nature (more in common with Smalltalk than C). Their business model
can be defined on the fly and changed at runtime. It's pretty powerful but you
always have the speed vs. size tradeoff. The BusinessQuery is a nice way to
send only the what you need to the server in a format that isn't too difficult
to translate to SQL but not so close to SQL that you couldn't rip out the
backend and use the same interface to communicate with something other than a
relational database.
With any tool you have to understand it's strengths and weaknesses. Express is
a 1.0 product. Given that I think they have done a great job. The biggest
request I have is that Express moves away from being so focused on UI and
Database access and focus more on the BusinessClasses. For example, why are the
Validate and NewObject methods not on the BusinessClass? I understand their
importance in the Window classes but they should really delegate most of the
work to the BusinessClass. Otherwise you end up with most of the logic in the
UI and a 2-tier application. One of the first things we did is extend the
Window classes to delegate validation, etc. to the classes they display.Paul,
This a very good point. After reviewing all the customizations we have done on
our Express project, (BTW, I work with Nabil) I found that we have not done any
business service customizations except for database row level security. We could
have easily moved validation to the business classes. Actually, Express gives you examples
for this. They recommend customizing the insert and update methods to apply validation.
You could simply add your own validate method on the business class and have the insert,
update, or the window call it. This is actually much more object oriented than coding
validation into the window classes (for the oo purest out there!).
Robert Crisafulli
AMISYS Managed Care Solutions Inc.
(301) 838-7540
>
I look forward to reading the white paper on Express. I would encourage anyone
else to post similar documents. If anyone is interested, I can dig up some
stuff I wrote on EOF's architecture. It's a good source for enhancement
requests if nothing else! If anyone has used other persistence frameworks I
think the group would benefit from their experiences.
Paul Krinsky
Price Waterhouse LLC
Management Consulting Group

Looking for best practice white paper on Internet Based Client Management

Looking for best practice white paper on Internet Based Client Management for SCCM 2012 R2.
Has anyone implemented this in a medium sized corporate environment? 10k+ workstations. We have a single primary site, SQL server and 85 DP's.

How about the TechNet docs: http://technet.microsoft.com/en-us/library/gg712701.aspx#Support_Internet_Clients ?
Or one of the many blog posts on the subject shown from a web search: http://www.bing.com/search?q=configuration+manager+2012+internet+based+client+management&go=Submit+Query&qs=bs&form=QBRE ?
Jason | http://blog.configmgrftw.com | @jasonsandys

E-Business Suite Application Dev using OAF and ADF (White Paper Feb. 2008)

Hi,
In Oracle White Paper entitled "E-Business Suite Application Dev using OAF and ADF (Feb. 2008)" it was mentioned on page 7 :
+"When ADF 11g becomes production, we will publish a revised paper that compares OAF with ADF 11g, and discuss development against E-Business Suite."+
I've had no luck finding a new comparison table for OAF R12 with ADF 11g :(
can anyone help me on this?
thanks in advance,
Adrian

Srini Chavali wrote:
It is still not clear if your have to use SSO - the scripts loadsdk.sql and regapp.sql specifically are for Oracle Single Sign ON (OSSO) - the authentication schemes referred to on page 20 of the same doc do not require SSO. So, is SSO a requirement in your scenario ? If not, you should be following the steps in the section titled "Confuguring Custom Authentication" (beginning of page 20).Ouch..Sorry Srini, I have completely misinterpreted by the page no.'s in Adobe pdf reader.I was telling you about page 18 of the document.
Anyway i'll start with configuring Custom Authentication as by your suggestion.
But i'll move forward with no understandings about SSO and its implementations.
All I could get is this links
http://docs.oracle.com/cd/E15586_01/webcenter.1111/e12405/wcadm_security_sso.htm
http://docs.oracle.com/cd/E15523_01/install.1111/e12002/sso_das.htm
Is this link correct to start learning about SSO or do I need to learn anything (LDAP,OAM,etc..) before that ?

Fixed assets white paper

Hi All.
Do you know if there is a document on fixed assets that outlines the capablities. Something that a client can read as they might be interested in using it.
Thank you

You may find Fixed assets online help file on the Portal. Although it is more than the white paper, the first few chapters could match your need without problem.
Thanks,
Gordon

Global Single Instance for R12 White Paper

Hello -
Please let me know any white paper for "Implementing Global Single Instance for R12".
We want to implement one Single Instance l[For eg : Accessing Single Instance for North America and Asia]
For this kind of architecture are there any specific documents or white papers from oracle.
Please let me know
Regards
VSH

Hi VSH;
Pelase check:
https://blogs.oracle.com/asparks/entry/global_single_instance_talking
http://www.oracle.com/us/corporate/press/017774_EN
Regard
Helios

Need very high PCIe throughput in your next design? Get help using Xilinx UltraScale, UltraScale+ devices in new White Paper

The Xilinx UltraScale architecture has many features that make implementing high-performance PCIe designs possible. Each of the integrated PCIe blocks in Xilinx Virtex UltraScale+ and Kintex UltraScale+ devices can transfer more than 14Gbytes/s in each direction sustained throughput when configured to operate as PCIe Gen3 x16 or Gen4 x8 port using a 256-byte system Maximum Payload Size and most UltraScale and UltraScale+ devices incorporate more than one such integrated PCIe block.
The transceivers in Xilinx devices based on the UltraScale architecture contain features that allow for very robust operation at these high PCIe data rates. These features include:
Transmitter emphasis/equalization
Auto-adaptive equalization
In addition, most PCIe applications use some type of high-speed memory for data buffering. Here again, Xilinx UltraScale and UltraScale+ devices provide for robust PCIe designs by supporting high-speed DDR4-2400 and DDR4-2666 SDRAM.
A new Xilinx White Paper, “PCI Express for UltraScale Architecture-Based Devices” (WP464), discusses these topics in much more detail.

The Xilinx UltraScale architecture has many features that make implementing high-performance PCIe designs possible. Each of the integrated PCIe blocks in Xilinx Virtex UltraScale+ and Kintex UltraScale+ devices can transfer more than 14Gbytes/s in each direction sustained throughput when configured to operate as PCIe Gen3 x16 or Gen4 x8 port using a 256-byte system Maximum Payload Size and most UltraScale and UltraScale+ devices incorporate more than one such integrated PCIe block.
The transceivers in Xilinx devices based on the UltraScale architecture contain features that allow for very robust operation at these high PCIe data rates. These features include:
Transmitter emphasis/equalization
Auto-adaptive equalization
In addition, most PCIe applications use some type of high-speed memory for data buffering. Here again, Xilinx UltraScale and UltraScale+ devices provide for robust PCIe designs by supporting high-speed DDR4-2400 and DDR4-2666 SDRAM.
A new Xilinx White Paper, “PCI Express for UltraScale Architecture-Based Devices” (WP464), discusses these topics in much more detail.

Difference between Web Client & Win Client (White Paper)

Subject: Difference between Web Client & Win Client
Dear all,
I know the Web Client and Win Client. But i want to know the exact difference between them? At this moment I am working an importante implementation
PS-CD with CRM and I need to evaluate Web Client and Win Client
Does anyone have a white paper about difference between Web Client and Win Client?
Or other documents related that can help me with these topics
I will real appreciate your support and help
Thanks in advance
Hiram Treviñ

Hi, send a test mail to this ID, [email protected] I shall send the documents.
Regards
Lakshman

Oracle NoSQL Database White Paper

Hi all,
I've just read Oracle NoSQL Database White Paper.
I would like to know the following:
1) Why should the number of partition be greater than the number of nodes? Is it because we can add more nodes after?
2) Is "Katana" a major, minor or major and minor key? Why don’t we see any major or minor key in this example?
3) For write operation: who propagates the operation to others nodes? Is it the client or the master node? In Implementation, I read the client does and in Architecture, I read the master does.
Thanks

user962305 wrote:
http://www.oracle.com/technetwork/database/nosqldb/learnmore/nosql-database-498041.pdf
Page 8 Paragraph Architecture see image «Figure 3 : Request Processing »In this example, there is only one component to the key ("Katana") so that is the master key. The Key factory method has several overloadings, one of which is just a single String (the major key).
>
The answer is that both client and server can forward the request depending on the situation. If a node receives a request that it can not handle (e.g. due to >> a mastership change), then the node will forward the request to the current master. If a client is not able to contact a node (e.g. the node is down), then it >> will redirect the request to a different node in the replication group.For a write operation. Who initially propagates the operation to others nodes? The client can contact master node and master applies the operation. Will the same client propagates the write to all other nodes or will the master contact all replication nodes in his group?Replication is always performed from the master, not the client. So any updates are sent from client to master and the master then propagates them to the clients. Reads, depending on the consistency level specified in the arguments to the API, may go directly from the client to any replica which can satisfy the request.
Charles Lamb

I have a line drawing (black on white paper) i have scanned and need to make the white paper transparent, maintaining the line drawing, can i and then HOW can i do this in PS?

i have a line drawing (black on white paper) i have scanned and need to make the white paper transparent, maintaining the line drawing, can i and then HOW can i do this in PS? this is for my business logo. ive used it for years but with a solid background. id like to have it just be the drawing over my photos with a transparent background.

First let me apologize for posting a reply that was only suitable for advanced users. Photoshop is broad and powerful therefore has a huge learning curve. In fact I would state no one knows and uses all of Photoshop. When we first get Photoshop it intimidate us and we're very uncomfortable using it. Many thing are not intuitive there in much learning involved. After some time we begin to know something and we are able to do some thing. Learning become rapid and we start playing in Photoshop. It is very important to play with Photoshop. Playing with Photoshop and asking for help with in forums like this IMO is the best way to learn.
Photoshop Power lies in layers, selection and automation. However it takes knowledge to use photoshop well so most powerful tool you have ins Photoshop is the gray matter between your ears. Most at one time or another want to watermark or put a logo on their image. So its best to automate this process. All run into a problem in the process. "Size" We find our assets vary in size and aspect ratios. Landscape, Portraits, Panoramas and others. This complicates automation. Vector graphics works best when size vary greatly. If you can not work out how to create a vector solution like a custom shape. Create your Logo and watermark large thing scale down better the up. Text scale well for text uses vectors graphics however if you rasterize text it will not scale well.
I do not type or do English well so let me do some screen captures. I can not stress enough how important Black, White, Grays and Blending is when it come to image processing. Become friends with Multiply, Screen, Overlay and Luminosity blending.....
However when there is a white or black background though you can blend them you can not add a style like a drop shadow, emboss or make it invisible setting fill to 0 so only the style is visible. When there is contrast between the logo and background it is easy to separate the two. To select the background and delet it to have the logo with a transparent background. Many tools can be used to create the selection hee I use my action kill white.
Vector Shape would work better for scaling However it would be best to create the logo from scratch in a vector program like illustrator but I never had the resources to justify the Creative suite. I only had Photoshop. Recently Adobe gave me and other a year subscription to the creative suite for our participation here. I still have not installed anything but Photoshop, A while back I found a program that can create vector patf for black and white art work. It will not be as good as using something like illustrator. However vector paths can be edited in Photoshop and cleaned up some. Here is the PSD it 13MB because od the gradient http://www.mouseprints.net/old/dpr/AmPm24-7.psd

Oracle Berkeley DB Java Edition High Availability (White Paper)

Hi all,
I've just read Oracle Berkeley DB Java Edition High Availability White Paper
http://www.oracle.com/technetwork/database/berkeleydb/berkeleydb-je-ha-whitepaper-132079.pdf
In section "Time Consistency Policy" (Page 18) it is written:
"Setting a lag period that is too small, given the load and available hardware resources, could result in
frequent timeout exceptions and reduce a replica's availability for read operations. It could also increase
the latency associated with read requests, as the replica makes the read transaction wait so that it can
catch up in the replication stream."
Can you tell me why those read operations will not be taken by the master ?
Why will we have frequent timeout ?
Why should read transaction wait instead of being redirect to the master ?
Why should it reduce replica's availability for read operations ?
Thanks

Please post this question on the Berkeley DB Java Edition (BDB JE) forum Berkeley DB Java Edition. This is the Berkeley DB Core (BDB) forum.
Thanks,
Andrei

Steps to configure R/3 system to Portal implementation

Hi
Please provide steps to configure R/3 system to Portal implementation
when i m opening standard iview in ESS in portal i m getting following runtime error.
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'SAP_R3_SelfServiceGenerics_MetaData' in the SLD. No such JCO destination is defined in the SLD.
Please help
Thanks

Hello Bhupinder Singh,
To use ESS/MSS services in Portal follow the following Steps
Maintaining jCo Connections
Use
jCo connections are used in iViews to connect directly to a backend. They are delivered with the portal content and must be activated (configured to access a specific system).
jCo connections have two parts: one with <jCo name>, and the other with suffix <jCo Name>_MetaData. The first one transfers user-specific data within the scenario; the other transfers only the needed metadata. For the jCo with name <jCo name>, SAP Logon Ticket is recommended as an authentication method. For the metadata connection, a user ID and password is needed. A system user created before is sufficient.
Procedure
Within this guide we generically describe the step-by-step procedure for an example connection set. Perform all steps for the following jCos:
u2022     SAP_R3_Financials / SAP_R3_Financials_Metadata
u2022     SAP_R3_HumanResources / SAP_R3_HumanResources_MetaData
u2022     SAP_R3_SelfServiceGenerics / SAP_R3_SelfServiceGenerics_MetaData
u2022     SAP_R3_Travel / SAP_R3_Travel_MetaData
u2022     SAP_R3_SelfServiceGenerics_MetaDataFIN
1.     Open the Web Dynpro Tool Applications overview page of your SAP NetWeaver Application Server Java: (http://<host>.<domain>:<port>/webdynpro/welcome)
2.     Select the Content Administrator link (or use a direct link, such as http://<host>.<domain>:<port>/webdynpro/dispatcher/sap.com/tcwdtools/Explorer) and logon with j2ee administrator rights
3.     Choose the Maintain JCo Destinations button.
4.     The available jCos are displayed with a red light, indicating that they are not yet maintained.
5.     In the JCo Destination Details iView, choose the Create button for the jCo you want to create.
6.     In Guided Procedure Section 1: General Data, make the following entries:
Field name     User action and values     Note
Name     <jCo_Name> or <jCo_name>_Metadata     Do not change the client number (for example, 100)
Maximal Pool Size     <keep default value>
Maximum connections     <keep default value>
Connection Timeout (msec.)     <keep default value>
Maximum Waiting Time (msec.)     <keep default value>
7.     Choose Next.
8.     In J2EE Cluster, make the following entries:
Field name     User action and values     Note
Use Local J2EE engine <SID> on <host>     Selected     Keep default values
9.     Choose Next.
10.     In Connection Type u2013 Data Type, make the following entries:
Field name     User action and values     Note
Data Type     Dictionary Meta Data     Dictionary Meta Data selected for <jCo_name>_MetaData; Application Data selected for <jCo_name> maintenance
Destination Type     Load-balanced Connection (recommended)     For Dictionary Meta Data Connection, the value cannot be changed
11.     Choose Next.
12.     In Msg. Server Connection, make the following entries:
Field name     User action and values     Note
Message Server     <select message server for your SAP ERP HR system>     The values are taken from the technical system list of the SLD
Logon Group     <select logon group for your SAP ERP HR system>     The values are taken from the technical system list of the SLD
13.     Choose Next.
14.     In Security u2013 User Authentication, make the following entries:
Field name     User action and values     Note
Used Method     <if using <jCo_name>, select Ticket>
<if using <jCo_name>_Metadata, value cannot be changed>
Name     <enter connection user name>     For example, rfcsysuser
Password/Confirm Password     <enter a password>
Language     English
SNC Mode     Off     For more information on SNC Mode, see the SAP NetWeaver 7.0 Help.
15.     Choose Next.
16.     In the Summary step, verify your settings, then choose Finish. The system displays a positive status message.
17.     In the JCo Destination Details iView, choose the Test link. The system displays a positive status message.
If the test fails, try to ping the ABAP system using the URL link. Check your settings, especially SLD, and certificate upload.
Let me know weather your problem solved or not.
Please reward points if helpful
Please close the thread if problem solved
Thankyou,
Regards
Vijai

How to resolve error in opening White Paper from OTN?

Attn: Oracle Reports Team
I want to optimize/tune my report. I was suggested from this forum to read White Paper available at http://otn.oracle.com/products/reports/pdf/275641.pdf.
I tried several times to open/print The white paper on above address but always got an error 'There was a problem reading this document (14)':
Previously I have been able to open and print white papers but here is some problem on the document side. Pl. guide as how I can I get this problem resolved.
Is Oracle Reports Team responsibel for resolving such problems or if there is some other department, let me know their contact so that I can take up matter with them. I need this white paper urgently as I am stuck up with a report. This report is taking 4 hours to process while expectation is 20 minutes.
Pl. help.
Tariq

I've just tried this with the following link and was able to download the paper without a problem:
http://otn.oracle.com/products/reports/pdf/275641.pdf
I'm using Acrobat Reader 5.0, but you may want to just try downloading again.
Danny

Looking for a Good White Paper on Oracle Data Modeling

Hopefully this is the proper area in which to ask this questions - been looking around these boards for a while but can't find what I'm looking for. I'd like to get a good modeling overview for topics such as:
-- pros and cons of normalization, e.g., performance considerations when deciding to normalize some data (and incur the cost of joins) vs keeping it denormalized (and having simpler queries)
-- overall performance considerations
-- warehouse vs mart considerations, esp as they relate to front end tools that will sit on the data mart
A general data modeling white paper or PDF would be very helpful to get me started.
Thanks all!
Mike

You don't need a White Paper you need a college course or a book.
The book I have on my shelf, don't know if it is still in print, is CASE*METHOD Entity Relationship Modelling by Richard Barker
Addison-Wesley Publishing Company
ISBN 0-201-41696-4
Normalization isn't about pros and cons. For performance denormalize. For data integrity normalize. Most systems end up somewhere between 3N and 4N or with what is referred to as Boyce-Codd NF. Google is your friend here but buy the book or take the course. This is not a subject to be read lightly in a dozen or so pages.

Portal Implementation : White Paper

Similar Messages

Maybe you are looking for