XI Architecture document

I would appreciate if anyone can send me the XI architecture document that you guys used for real XI implementation at the customer/client site. I surely would reward with points.
Pam

If you are looking for ASAP of SAP XI this link should help you - http://media.sdn.sap.com/html/submitted_docs/Implementation_Roadmap_XI/index.htm
but in case you are looking at the Xi arch. in terms of its connectivity and build - https://websmp205.sap-ag.de/xi

Similar Messages

Creating an Architecture Document For a Portal

I have been asked to come up with an Architecture Document for a public facing SharePoint 2010 site. I am familiar with the SharePoint 2010 technologies, however I need a starting point on where and how to start the Architecture document. Is there any Architecture Template Document that exists so that I can use them?

Hi
I cannot share the full and final doc with you but following Index will help you creating the Architecture document from the scratch
1     Document Overview............................................................................................................ 7
1.1     Scope............................................................................................................................... 7
1.2     Audience......................................................................................................................... 7
2     Logical Architecture............................................................................................................ 9
2.1     Overview.......................................................................................................................... 9
2.2     Diagram........................................................................................................................... 9
2.3     Component Description.............................................................................................. 9
3     Physical Architecture....................................................................................................... 11
3.1     Overview....................................................................................................................... 11
3.2     Production Environment.......................................................................................... 11
3.2.1     Diagram................................................................................................................... 11
3.2.2     Component Description....................................................................................... 12
3.2.3     Hardware Requirements...................................................................................... 14
3.2.4     Software Requirements........................................................................................ 14
3.3     Staging Environment................................................................................................. 14
3.3.1     Diagram................................................................................................................... 15
3.3.2     Component Description....................................................................................... 15
3.3.3     Hardware Requirements...................................................................................... 15
3.3.4     Software Requirements........................................................................................ 16
3.4     Development & Test Environment......................................................................... 16
3.4.2     Diagram................................................................................................................... 16
3.4.3     Component Description....................................................................................... 17
3.4.4     Hardware Requirements...................................................................................... 17
3.4.5     Software Requirements........................................................................................ 18
4     Non-Functional Requirements....................................................................................... 19
4.1     Security......................................................................................................................... 19
4.1.1     Requirements......................................................................................................... 19
4.1.2     Authentication........................................................................................................ 19
4.1.3     Authorization.......................................................................................................... 19
4.2     Availability..................................................................................................................... 21
4.2.1     Requirements......................................................................................................... 21
4.2.2     Hardware Redundancy and Failover................................................................. 22
4.2.3     Scaling Logical SharePoint Components......................................................... 22
4.2.4     Disaster Recovery.................................................................................................. 22
4.3     Performance................................................................................................................. 23
4.3.1     Requirements......................................................................................................... 23
4.3.2     Performance & Capacity Expectations.............................................................. 23
4.3.3     Size and Volume Assumptions.......................................................................... 23
4.3.4     Performance Testing Approach.......................................................................... 25
4.3.5     Performance Tuning Approach.......................................................................... 25
4.3.6     Monitoring and Reporting.................................................................................... 26
4.4     Accessibility................................................................................................................. 26
4.4.1     Requirements......................................................................................................... 26
4.4.2     Internal Access....................................................................................................... 26
4.4.3     Remote Access...................................................................................................... 26
4.5     Auditing & Reporting................................................................................................. 27
4.5.1     Requirements......................................................................................................... 27
4.5.2     Approach................................................................................................................. 27
4.5.3     Audit Reports.......................................................................................................... 27
4.5.4     Diagnostic Logging............................................................................................... 28
4.5.5     Portal Usage Reporting........................................................................................ 28
4.6     Exception Handling & Logging............................................................................... 28
4.6.1     Exception Handling............................................................................................... 28
       Application..................................................................................................................... 29
4.6.2     Logging.................................................................................................................... 29
4.7     Caching......................................................................................................................... 29
4.7.1     Disk based caching for BLOBs........................................................................... 29
4.7.2     Client-side caching............................................................................................... 30
4.7.3     Object Caching...................................................................................................... 30
4.8     Maintainability.............................................................................................................. 31
4.8.1     Backup and Restore.............................................................................................. 31
4.8.2     Archiving & Purging.............................................................................................. 32
4.9     Regional Deployment................................................................................................ 32
4.9.1     Conceptual Diagram............................................................................................. 32
4.9.2     Feature Summary.................................................................................................. 33
4.10      Service Management.............................................................................................. 35
5     Search Architecture.......................................................................................................... 36
5.1     Introduction.................................................................................................................. 36
5.2     Key Design Considerations..................................................................................... 37
5.2.1     Distributed Geographical Deployment............................................................... 37
5.2.2     Content Sources.................................................................................................... 37
5.2.3     Availability & Performance................................................................................... 37
5.2.4     Physical Infrastructure.......................................................................................... 38
5.2.5     Search as a Shared Service................................................................................ 38
5.3     Search Architecture in portal..................................................................................... 38
6     Content Deployment Architecture................................................................................ 41
6.1     Introduction.................................................................................................................. 41
6.2     Key Design Considerations..................................................................................... 41
6.2.1     Distributed Geographical Deployment............................................................... 41
6.2.2     Security.................................................................................................................... 42
6.2.3     Availability............................................................................................................... 42
6.2.4     Publishing Frequency.......................................................................................... 42
6.2.5     Physical Infrastructure.......................................................................................... 42
6.2.6     User Contributed Content.................................................................................... 42
6.3     Content Deployment in portal................................................................................... 43
7     References.......................................................................................................................... 45
8     Key Decisions.................................................................................................................... 46
9     Dependencies.................................................................................................................... 47
10      Key Contacts................................................................................................................... 48
11      Appendix A – Active Directory Requirements........................................................ 49
12      Appendix B – Capacity Sizing Model........................................................................ 51
13      Appendix C – Hardware & Software Requirement Summary............................. 53
14      Appendix D – Site Architecture................................................................................... 55
Regards
Deepak Aggarwal

Reg: WPC application architecture document

Hi,
We are looking for extending the WPC (Portal 7.3) features...
Is there any documentation around the new WPC (Portal 7.3 )application architecture where we can find the UI classes and services/backend classes api to publish the documents,creation of folders,creation of area and etc..
We know that below interfaces are available to extend the WPC, but we are looking more than this.
com.sap.portal.wpc.api.content
com.sap.portal.wpc.api.content.handler
com.sap.portal.wpc.api.content.provider
Thanks & Regds,
JC

Hi,
We are looking for extending the WPC (Portal 7.3) features...
Is there any documentation around the new WPC (Portal 7.3 )application architecture where we can find the UI classes and services/backend classes api to publish the documents,creation of folders,creation of area and etc..
We know that below interfaces are available to extend the WPC, but we are looking more than this.
com.sap.portal.wpc.api.content
com.sap.portal.wpc.api.content.handler
com.sap.portal.wpc.api.content.provider
Thanks & Regds,
JC

Micro-architecture documents

Hello:
Besides your IEEE MICRO paper, I'm unable to find any documentation about the Niagara's micro-architecture. More specifically, I'm looking for details such as: L2 cache bank conflict penalty, are the caches -indexed and -tagged using physical addresses, FPU exposed pipeline latency etc. Digging out this information from the RLT seems impossible. I know that Intel has such documents for the Itanium processor (called: Processor Reference Manual for Software Development and Optimization). Are there any such document for the Niagara? Thank you,
-ram

Sun is working hard to release much more detailed micro-architecture information. I don't know the exact schedule, but either it was just released in the OpenSPARC T1 source code "tar-ball", or will be in a release coming soon. I'm not sure if it will be in the "tar-ball" or separately downloadable -- I will check with some others here and see if I can get them to post a more authoritative response in this thread.
= Dave

FPM architecture documents links

Hi All
Please provide me FPM documents links
Thanks
Karthi D.

Karthi,
check these links
SDN Day session in Las Vegas: Custom development of Web Dynpro ESS applications using Floor Plan Manager
http://help.sap.com/saphelp_erp2005/helpdata/en/b4/139525380149a49c8402e22700e4ba/frameset.htm
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/9f/95467bbefc4a808fffeba4c5177258/frameset.htm
Thanks
Bala Duvvuri

Intro to UltraSPARC Architecture 2005

(this posting is cross-posted in my blog, http://blogs.sun.com/roller/page/dweaver)
Not only is the OpenSPARC T1 processor the first open-sourced 64-bit processor implementation, but it (and its twin, UltraSPARC T1/Niagara) are the first processors that adheres to Sun's new processor architecture specification.
With this posting, I'll embark on a series of posts to introduce this new processor architecture, named UltraSPARC Architecture 2005. We're completing the final touches for external publication of the actual specification; it should be posted on the web (on http://OpenSPARC.net) and the Sun processor web site (http://www.sun.com/processors/documentation.html) within a month.
To be notified when the architecture spec is posted, Login (http://www.sunsource.net/servlets/TLogin) to the OpenSPARC site and visit the OpenSPARC mailing list page (http://opensparc.sunsource.net/servlets/ProjectMailingListList) to register for the opensparc-announce mailing list.
The first question many people (even some inside Sun!) ask about the UltraSPARC Architecture is "why is a new architecture specification needed? Can't/shouldn't we just refer to the existing SPARC V9 specification plus a User's Guides for specific processors, like we've done in the past?"
Well, we could have continued down that path. However, it would have required software developers (probably the largest group of readers) to consult not just two, but multiple documents ... primarily SPARC V9 plus various processor implementation documents. With the UltraSPARC Architecture, readers can go to a single document to understand all they need to know about a whole generation of UltraSPARC processors, with all the most up-to-date information. A few may also want to consult implementation-specific architecture supplements.
Other factors motivating the UltraSPARC Architecture document involve the state of the SPARC V9 specification: <ul> <li> it is now over 10 years old </li>
<li> its hardcopy version contains ~90 known errata (enumerated at http://www.sparc.com/standards/v9-errata.html) ... although the PDF softcopy at SPARC International (http://www.sparc.com/standards/SPARCV9.pdf) has been updated with corrections to those bugs </li>
<li>doesn't enumerate all exception-causing conditions for each instruction</li>
<li>contains many ambiguities (one example: trap priorities) </li>
<li>doesn't contain any of the numerous standard Sun extensions (many of which have been present for over 10 years).
(fortunately, I can say all that about SPARC V9 without fear of insulting its editor ;-))</li> </ul>
The UltraSPARC Architecture 2005 specification: <ol> <li>describes processor behavior much more precisely than did SPARC V9</li>
<li>describes all the Sun architectural extensions (for example, VIS 1 and VIS 2 instructions, GSR register, and global register sets)</li>
<li>won't be a static document -- if/when documentation bugs are identified, they will be fixed and a revised version will be posted on the web</li> </ol>
Ambiguities that were present in SPARC V9 have been cleared up whereever possible in the UltraSPARC Architecture document -- and when not, are spelled out as explicit implementation dependencies. In each instruction description, all exceptions that can be triggered by the instruction are now listed, along with the precise conditions that can cause each exception. Whereever possible, old implementation dependencies were resolved and closed, so there are fewer gratuitous differences between implemenations.
Does this specification replace SPARC V9? Yes and no. SPARC V9 is still the <i>standard</i> by which (64-bit) SPARC implementations are measured; compliance with it is a prerequisite for using the trademarked name "SPARC". And SPARC V9 covers 64-bit SPARC processors from all vendors (primarily Sun and Fujitsu, as I write this), whereas the UltraSPARC Architecture only applies to UltraSPARC processors (and to OpenSPARC T1). For anyone using a Sun UltraSPARC or OpenSPARC T1 processor, the UltraSPARC Architecture spec should be the reference of choice.
In subsequent postings, I'll assume that the reader has at least passing familiarity with the SPARC instruction set architecture, and will begin describing the new features specified in the UltraSPARC Architecture 2005 -- including Hyperprivileged mode, Chip Multi-Threading (CMT) control, new global registers set organization, new privileged instructions, and how UltraSPARC Architecture is set up to smoothly evolve over the coming years while continuing to maintain compatibility for existing SPARC application binaries.
David Weaver
UltraSPARC Architecture
Sun Microsystems / Scalable Systems Group (SSG)

The first question many people (even some inside
Sun!) ask about the UltraSPARC Architecture is "why
is a new architecture specification needed?
Can't/shouldn't we just refer to the existing SPARC
V9 specification plus a User's Guides for specific
processors, like we've done in the past?"
Well, we could have continued down that path.
However, it would have required software developers
(probably the largest group of readers) to consult
not just two, but multiple documents ... primarily
SPARC V9 plus various processor implementation
documents. With the UltraSPARC Architecture,
readers can go to a single document to
understand all they need to know about a whole
generation of UltraSPARC processors, with all the
most up-to-date information. A few may also want to
consult implementation-specific architecture
supplements.
Other factors motivating the UltraSPARC Architecture
document involve the state of the SPARC V9
specification: <ul> <li> it is now over 10 years
old </li>
<li> its hardcopy version contains ~90 known errata
(enumerated at
http://www.sparc.com/standards/v9-errata.html) ...
although the PDF softcopy at SPARC International
(http://www.sparc.com/standards/SPARCV9.pdf) has been
updated with corrections to those bugs </li>
Does this specification replace SPARC V9? Yes and
no. SPARC V9 is still the <i>standard</i> by which
(64-bit) SPARC implementations are measured;
compliance with it is a prerequisite for using the
trademarked name "SPARC". And SPARC V9 covers 64-bit
SPARC processors from all vendors (primarily Sun and
Fujitsu, as I write this), whereas the UltraSPARC
Architecture only applies to UltraSPARC processors
(and to OpenSPARC T1).
UltraSPARC
Architecture is set up to smoothly evolve over the
coming years while continuing to maintain
compatibility for existing SPARC application
binaries.David,
The description at
http://opensparc-t1.sunsource.net/index.html
states that "UltraSPARC Architecture 2005 complies with SPARC V9 Level 1". Does it not comply with Level 2? Will this present a problem (i.e. binary compatibility) for developers of supervisor software targeting e.g. UltraSPARC and Fujitsu's SPARC64 family?
Alan Feldstein
Cosmic Horizon
http://www.alanfeldstein.com/

Netweaver Technical Architecture

Hi,
Has anyone come cross the technical architecture document for all SAP Netweaver components? SAP provides installation guide for each Netweaver component which have pretty good example of the technical architecture view. But I haven't seen any tech. arch. document connect all the dots.
Thanks,
Richard

That is something to answer directly:
- does XI have to be on
> a different server?
XI itself usually is sitting on different servers, once its getting a little bigger. You can see that from their architecture easily.
However, it is possible to install NetWeaver completely on one machine. But this seldomly makes sense, if ever.
can it be installed on the MDM
> server?
This really depends.
what is SAP's recommendation if the company
> want to implement the whole NetWeaver product suites?
This is very individual and depending.
> It is difficult to decide what you can and can't do
> when you try to put a tech arch doc together for
> multiple NetWeaver components.
Well, we're on the way. A couple of years from now I guess you will see a single installation that always has complete NetWeaver in it (due to growth of memory in general), because then the ressources are cheaper then the effort to do different installations.
Regards,
Benny
>
> Thanks,
> Richard

Architecture of Oracle Stellent

Hi,
Can anyone please pass on the document that has the Architecture of Oracle Stellent, with Add ons listed as well?
if not, a simple architecture document will also do.
Thanks,
-Sahil Gupta

Hello -
First of all the best for your Thesis and appreciating for selecting Oracle BPM.
Check this : http://www.oracle.com/technetwork/middleware/bpm/obpm-articles-086639.html
Most of the articles are by Mariano Benitez - BPM Architect.
BR,
Justin.

Re: architecture question

By all means, you should use common API's, objects, and methods wherever
possible. This is what object-oriented design is all about. A client name
and address, for example, is still a name and address, whether it is being
used by a claim examiner, an underwriter, or a customer relations
representative. Coverage information does not change just because you are
displaying it in a claim system rather than a policy system. And claim
information is still claim information even when it is being reviewed by an
underwriter.
Having been in the insurance business previously, I know there is a common
notion that, for example, Policy systems and Claim systems are separate, and
that each wants to keep its own vision of the world. And, there may be
instances where the data presented may vary somewhat from one system to
another.
For example, a claim system might display only summary policy information
and vice versa. However, you should still use policy system methods and
API's to retrieve and display the policy data, and claim system methods and
API's for the claim data.
Even if you ignore the tremendous benefits to be derived from re-usable
code, think of the advantages for your end-users. If you can achieve a
consistent look and feel across systems, then users do not need to remember
that claim systems does things one way and policy systems presents the same
information in an entirely different manner.
Some people do not like the concept of data "ownership." However, when you
get into an environment where complex data is shared enterprise-wide,
someone must be the keeper of the rules. Without that, you can introduce
integrity problems with the data itself, as well as interpretation problems
when different systems treat the data differently. The owner of the data is
not the application or the system - it is the person or group of people who
have the right to determine how that data is used, updated, and interpreted.
An application or system will frequently combine data from multiple "owners"
or "rule keepers." Using methods that belong to the owner of the data helps
assure that the data is being used and interpreted properly.
Did this address your concern adequately?
At 08:57 AM 10/15/96 -0600, [email protected] wrote:
Dear Forte users:
This is not directly related to Forte, but I hope I can get some insights from
the collective wisdom. I was reviewing an architecture document regarding
insurance applications and came across a statement that troubles me and I
appreciate if you could comment on that.
The statement goes:
Access to common or shared data is provided via API's by the application
that owns and maintains the data.
My concern is that should an application own the data, specially in an
environment where there exist multiple application systems (e.g., policy
systems, claims systems, etc.). Should my claim systems have to use my policy
systems API's in order to have access to the client information? If not, what
about data integrity?
Does this make sense to anyone, especially in a heterogenous multi-tier
environment?
You comments are appreciated. Thanks,
/Farhad
--Jeanne
=====================================================================
Jeanne Hesler [email protected]
=====================================================================

[email protected] wrote:
>
Dear Forte users:
This is not directly related to Forte, but I hope I can get some insights from
the collective wisdom. I was reviewing an architecture document regarding
insurance applications and came across a statement that troubles me and I
appreciate if you could comment on that.
The statement goes:
Access to common or shared data is provided via API's by the application
that owns and maintains the data.
My concern is that should an application own the data, specially in an
environment where there exist multiple application systems (e.g., policy
systems, claims systems, etc.). Should my claim systems have to use my policy
systems API's in order to have access to the client information? If not, what
about data integrity?
Does this make sense to anyone, especially in a heterogenous multi-tier
environment?
You comments are appreciated. Thanks,
/FarhadI would agree with the above statement, if you substitute the word
"service", for the word "application".
If you follow the notion of a service-based architecture, and have a
service own and provide access to a set of data objects, then the
problem vanishes. Any number of applications can gain access to the data
via a service that has a public interface. No one application would have
ownership of the data - the data access service does. In a service-based
architecture, the notion of an appliction becomes a bit fuzzy. An
application is a pacakaging of a certain set of service requests from
public servers, usually through some human-computer interface. Once you
have your services defined, you can think of many ways to deliver them
via "applications". Things would probably be a lot clearer if the notion
of an application is not used at all. Concentrate on defining services.
Means to deliver the services would vary over time. You may start with a
batch update, and report cycle, then go to a window-based application
(GUI). Some of your users may want web-based forms via their intranet
browser as their "application".
A good model to emulate would be the Object Management Architecture from
OMG.
Hope that helps.
==================================================
Nabil Hijazi Optimum Solutions, Inc.
[email protected] 11654 Plaza America Drive
Phone: (703) 435-3530 #501
Fax: (703) 435-9212 Reston, Va 20190
--------------------------------------------------

Architecture of new Petstore application

I was wondering if there is any architecture document of the new Petstore application that uses JSF, AJAX, JMaki etc.
If yes, then what is the URL of the document
Thanks
-Sankate

Hi,
1. The Map module in particular, most the websites
using Google mashups do not require so much server
side plumbing, any particular reason of this
approach?The page that displays the maps (you can see a live demo at http://webdev2.sun.com/petstore/faces/mapAll.jsp and click "Map Category") has a lot of features. Beside just using the google map APIs to show a map with data points pulled from PS, it also dispays a list of items in a left side bar with pop up balloon details) So for one thing it has some extra features so some extra code.
Using the google map Javascript library to just display the google map on a page with data provided from your app can be simpler, you could just use the google map Javascript library APIs directly in the page.
In our case we decided to wrap that map functionality into a JSF component so that people could re-ues the functionality. It can be tricky to build a JSF component and the coding burden is placed on the component developer, but once you have a JSF component it can be easy for the page author to use the JSF component. We use the same mapping JSF components in several apps and it is alos included in some tools etc, so re-use was useful in our case. For another app, you might not need to wrap it in JSF.
Wrapping in JSF does add some extra plumbing code.
So in general, wrapping a JS library like google maps in a JSF component, can have some extra work, but some benfits as well. It depends how you plan to use the functionality, if you plan for re-use then JSF is one way to accomplish this. It imposes a certain architecture on that functionality.
Also, in terms of back end plumbing, also you do need a web request on youre server to process the request, and return a page with UI and data. We stroed the data in a database so this has some backend code as well. For example, that page displays a list of pets in that area in a left side bar, so need to persist and retrieve that data from DB. Also, google maps requires longitute and latitute, so you need to get that data too. Since we store addresses for each Item (pet info) in the DB, and google needs latitude and longitude, when we add a new address ad Item to DB, we also use yahoo geocoding service mashup to lookup cooresponding latitude and longitude and store that along with other address data, so we dont have to look it up from yahoo for each client map viewing request, instead we can just pull the info from DB along with other Item info.
So there is some necessary extra data and plumbing and coding required, even if you do not wrap it in a JSF component.
hth,
Sean

InDesign/InCopy 7.5.3 is out [ANN]

You can tell CS6 is getting close.
Adobe has released InDesign and InCopy (and InDesign Server) version 7.5.3.333.
Release notes at http://helpx.adobe.com/indesign/release-note/release-notes-indesign-cs5-51.html
(well, linked from http://www.adobe.com/support/documentation/en/indesign_incopy/releasenotes.html#indesignCS 55753 if you want to compare InDesign and InCopy and InDesign Server).
Changes from 7.5.2.318 to 7.5.3.333:
Architecture / Document
InDesign unexpectedly quits when performing certain copy/paste operations. [3073952, 2941163]*
When opening files from a newer version of InDesign, non-meaningful errors about missing plug-ins are shown rather than a clear indication that the file is from a newer version. [2944763]*
Degradation in performance when moving objects when display is set to High Quality [3128109]*
InDesign unexpectedly quits when recovering a file on product restart. [3100953]*
Graphics
White stitching line in JPEG export with certain placed images scaling percentage and JPEG export resolution [2987040]*
Redraw performance for ID CS5 is slow compared to CS3. [2910574]*
Poster: From Current Frame' option in the Media will not restore the poster from that frame after re-linking. [3097841]*
Reduced transparency support for TIFF files from Photoshop CS6 [3073238]*
Hyperlinks
In certain drag and drop scenarios, URLs are getting changed in InCopy/InDesign CS4, CS5.5 [3054805]*
Installer
Uninstall/Reinstall removes Bridge's "Place>In InDesign" menu item. [3079235]*
Import / Export
Wrong page number on export book to PDF [2940448]*
INX / IDML
Tab override gets reset in INX/IDML [2827174]*
Master applied incorrectly when opening IDML file [3114965]*
Legacy versions fail to read ID CS6 files that contain files with new Pantone Plus colors. [3119501]*
Layout
Inconsistency in loading and exporting a linked image from INDD [3017929]*
Strange offset occurs between two pages on same spread [3080049]*
Print / PDF
InDesign unexpectedly quits when exporting to PDF with text variables [2866963]*
Note inside document table with text variable causes InDesign to quit unexpectedly on export to PDF/IDML. [3089441]*
Unable to navigate document if TOC is on master page. [2907482]*
Text appears misplaced in certain cases when DataMerge is used to export [2939067]*
InDesign hangs or quits unexpectedly during certain package and preflight operations. [2982454]*
Scripting
Problem copying stories via VBScript when called through an application [3059225]*
Unexpected shutdown when JavaScript is executed with InDesign followed by closing of document. [3021908]*
Text
Using Smart Layout with Linked frames causes InDesign to unexpectedly quit in certain cases. [3085379]*
Fonts not loading from different locations. [3013562]*
InDesign quits unexpectedly with certain fonts when balancing columns [3099740]*
Fonts of the same family but different type behave unexpectedly on IDML round trip. [3114961]*
Certain documents go into infinite loop when adjusting frame size [3113902]*
Incorrect glyph selection with certain Indic fonts when using specific virama and joiner character sequences. [2849232]*
Broken spanning columns cause issues with Text Wrap & Keeps Options [2958674]*
UI
Folio Builder and CS Review's SWFs will not render when '<' is present in doc filename [2971572]*
InDesign CS5.5 quits unexpectedly on deleting unused swatches using small view option [2987294]*
XML
associatedXMLElement returns 'NULL' for a merged cell in table. [2946288]*
InDesign Server Only
CCommandLineArgs::ProcessArgsLate will cause product to hang in certain cases when used with LogToApplicationEventLog [2988814]*
InDesign Server quits unexpectecly when running spell checker on certain documents. [2935990]*
Document installed fonts get locked on Windows. [2890001]*

Hey, what about this one!
When opening files from a newer version of InDesign, non-meaningful errors about missing plug-ins are shown rather than a clear indication that the file is from a newer version. [2944763]*
This needs to be retro-fixed for all existing versions, all the way back to InDesign 1.0!
It's unimaginable this particular issue had to persist for more than a decade, leading to frustration and bewilderment of literally thousands of users, and hundreds upon hundreds of posts in this forum alone.

PDF won't open in Acrobat after Saving in illustrator

Hi I am currently working on my final architecture project and am having issues with opening a PDF in acrobat after editing and saving in Illustrator.
I am creating an architecture document in autocad which I then export to PDF to be edited in Illustrator. It opens fine in illustrator, however once I have edited and saved in illustrator I am unable to open in acrobat and the program just crashes.
After editing in illustrator the file size increases fairly substantially, but I am able to open larger PDF files no problem if they have no been edited in Illustrator.
Any help would be great. Let me know if any further information would help?
Thanks!

Hi Graffiti,
I have posted it in the windows one as I am using Autocad in windows to create the origional PDF. However this has not caused any problems until now.
In answer to your other questions I have used 'save' and 'save as' and tried saving under new file names.
I have been saving the PDF rather than using the PDF printer.
Let me know if any other info would help.

Flex Developer Opening (Singapore)

Looking for a number of Flex Developers/consultants for
opening in Singapore
Responsibilities:
Develop web user interfaces, style sheets, templates and
layouts for use in projects, product development/implementation and
maintenance-support.
Create sitemaps, wireframes (HTML/XHTML) and other
architectural documents, as needed, based on firm understanding of
UI and navigation planning.
Conceptualize requirements into creative, dynamic and rich
UI.
Ensure site design integrity and quality control.
Stay knowledgeable of the industry standards and trends.
Applying methodology (e.g. OO, RUP, Agile) to prepare
high-level design documents.
Requirements:
1+ year experience in professional experience in design,
coding, and corporate branding.
Knowledge of building rich web interfaces and architectures
and proven experience of web development technologies and
frameworks.
Knowledge of HTML / CSS and web standards.
Working knowledge of Macromedia Flash, ActionScript 2 / 3.
Working experience in Web Technology such as Java and
Flash/Flex.
Knowledge and understanding in integration technology such as
J2EE is a plus.
Excellent technical, analytical and communication skills.
Strong team player, able to work successfully with
cross-functional, geographically dispersed teams.
Interested, please email to [email protected]
Thank you.
Regards,
MK

You should also crosspost this at
http://www.cflex.net/ and the Flex
jobs yahoogroup.
hth,
matt horn
flex docs

Using XI in Data Migration World

Hi,
We are thinking to use XI as a replacement to ETL tool in our typical data migration activities.
1) Is it easy to do XI for data migration activities like converting Materials, Vendors,Customers, etc? There will be significant cleaning & profiling of data. Is that possible using XI?
2) Do we still need to use staging database? Any architecture document or white papers covering DM-XI will be very helpful
3) We have several legacy systems to convert in phases and I am looking for any best standards of practice using DM with XI.
Any additional information on conversions with XI is very useful.
Thanks,
Subbu

Hi,
If u think only for data migration purpose Xi is not suugestable, since we need to convert large volume of data. We have standard programs also if u want convert data into SAP.
XI is could be useful to fetch the data from legacy and post the needed information into target system by converting suitable format.
Regards,
venu

JAX-WS 2.1 FCS is released

We are proud to announce the release of JAX-WS 2.1 RI FCS. JAX-WS 2.1 is
a major re-architecture over JAX-WS 2.0 without changing the standard
JAX-WS APIs or programming model. The benefits of this is a very fast
implementation and an extremely flexible, extensible architecture. To
read more about how fast the RI is and the new functionality that it
contains, read Vivek's blog at:
http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
Here is an excerpt from Vivek's blog about the Key Features.
* Reference Implementation (RI) of JAX-WS 2.1. Full JAX-WS 2.1
Specification <http://jcp.org/en/jsr/detail?id=224> compliance
* Development Tools
o WSDL to Java generator
+ Wsimport command line tool
<https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>, ant task
<https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html and
Maven2 plugin
<http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
o Java to WSDL generator
+ Wsgen command line tool
<https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>, ant Task
<https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>
and Maven2 plugin
<http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
o Integrated with NetBeans 5.5.1
<http://www.netbeans.info/downloads/dev.php>
* Standards
o Web Services Addressing 1.0 - Core, SOAP Binding and WSDL Binding
o WS-Addressing - Member Submission
o SOAP 1.1 and 1.2
o REST and XML/HTTP
o WS-I Basic Profile 1.1, Simple SOAP Binding Profile 1.0 and Attachment
Profile 1.0
o MTOM
* Extensions (May not be final unless says so)
o Web Services Interoperable Technologies ( WSIT
<https://wsit.dev.java.net/index.html#downloads>) - enables .NET 3.0
interoperability
+ WS-ReliableMessaging
+ WS-Policy
+ WS-MEX
+ WS-Security/WS-Security Policy
+ WS-Trust/WS-Secure Conversation
+ WS-AT/WS-Tx (Supported only on Glassfish v2)
+ SOAP/TCP
o Spring support <https://jax-ws-commons.dev.java.net/spring/>
o Pluggable Transport <https://jax-ws.dev.java.net/transport.html>
+ In-VM transport
+ Servlet transport (bundled with the RI)
+ JMS transport <http://jms-ws-transport.dev.java.net/>
+ SOAP over TCP transport (part of WSIT <https://wsit.dev.java.net>)
o FastInfoset (bundled with JAX-WS 2.1 RI) <https://fi.dev.java.net/>
+ ITU-T Rec. X.891 | ISO/IEC 24824-1
<http://www.itu.int/rec/T-REC-X.891-200505-I/e>
o JBI Service Engine and Binding Component(part of Glassfish v2)
o HTTP Binding Component
<http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>,
used by Open JBI component <https://open-jbi-components.dev.java.net/>
* Data binding - JAXB 2.1.2 RI <https://jaxb.dev.java.net/2.1.2/>
* Server Side Asynchrony - AsyncProvider
<https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>
* Stateful Web Services
<https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>
* Support for custom WebServiceFeature
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.html>
* Hosting API
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/sun/xml/ws/api/server/package-summary.html>
o These APIs can be used by a J2EE application server to integrate JAX-WS
2.1 RI for hosting JAX-WS services
* Endpoint Deployment
o Glassfish v2 <https://glassfish.dev.java.net>
+ Tightly integrated with Glassfish
+ Supports EJB and Web endpoints
+ 109 based deployment support for better portability
+ JAX-WS RI specific deployment descriptor support
o Sun One Application Server 9.0 ur1
<http://www.sun.com/software/products/appsrvr_pe/index.xml>
o Light weight HTTP server
+ On JDK 1.5 through http.jar distributed with the JAX-WS 2.1 RI bundle
+ Bundled with JDK 6
o Any other container that supports Servlet 2.4, such as Tomcat, Jetty,
Geronimo, JBoss, Resin, ... You name it!

Didn't find the solution for this, but any object that contains an Object in its methods / attributes had the same problems, so i just built my own table that only supports Strings and the problem was solved.
If anyone knows why i had this problem and wants to share a solution, please do so.

XI Architecture document

Similar Messages

Maybe you are looking for