Portal Content Deployment - History

Hello Gurus
Is there is a way to figure out the list of all the portal contents deployed in the portal. ( including date and time).
On the ABAP stack we have import history and we can check list of transports, in same way how can see the list of portal contents deplyed to PORTALS.
Appreciate your help.
Regards
Rrs

Ratan,
Interesting topic - it would depend on how your group has been exporting content (assuming that you are talking about Portal Content and not Java Development). By default, the export tool will overwrite the previous export file if you don't have a procedure in place to make new files for each export. Other then that, I don't think that there is a log of activity or content. For this I nornally require my content admins for Portals to create a unique folder for each project, a sub-foler for each section, and a single file for each export - adding a revision number to the end of each file as they export them.
A long explination for - the system doesn't do it but you can setup something so you can manage it yourself.
My method above helps to keep things in order and you can go look back at the export files and what was in them for this purpose. I also change the export/import directory for the Dev to QA Portal so Basis doesn't need to baby-sit the developers moving content between those two systems and so Developers don't need access to the file system. (Dev export directory is on an NFS between Dev and QA - QA import points to the NFS Dev export folder - so you can just import without doing anything). Somewhat like TMS - for prod I still have an NFS but Basis moves the files to the right import directory.
Hope that helps somewhat to get you going. May seem like overkill but when you get 5-10 portal developers moving quickly, it helps to keep it all in synch with the ECC transports!!

Similar Messages

Transporting/Deploying Portal Content and Delta Linked Objects

I researching the best way to trasport/deploy changed ESS Portal content from sandbox to D>Q. I have become familiar with the few changes my co. needs to deploy part of ESS. I have read articles that say it is wrong to modify the "Content Provided by SAP". The recommendation appears to be "use delta link objects". I created the necessary delta links in a new directory.
How do I get the delta link objects to display instead of the sap source objects? I this primarily related to how the portal is configured or how the content is managed?
I'm really sorry about the general question (in advance) but this stuff is new for me and I'm essentially looking for some good direction here.
Thanks,
James

Hi James,
Yes exactly right. You should create your own PCD folder under Portal Content to store your objects. How you structure that is entirely up to you, however in my experience I have seen two ways
1. First by Function or Dept (e.g. Finance, Logistics, HR) then by technical object (iView, role etc...)
2. First by Technical Object (e.g. iViews, Roles, Worksets etc...) then by function or dept or region (Finance, HR etc...)
Number 1 makes more sense to me. Just some other tips when it comes to creating PCD content:
1. Put everything in your own namespace (e.g. com.mycompany) that way it is easy to separate from SAP content using filters.
2, Come up with a logical naming standard so you can easily identify content by group, function and technical type (e.g. for an iView you might name it whoswho with the prefix com.mycompany.hr.ivu resulting in a name com.mycompany.hr.ivu.whoswho)
2. Don't give PCD folders any prefix (e.g. com.mycompany) as it ends up elongating the resulting URLs unnecessarily and you can run into problems down the track.
Hope this helps you.
Simon

Dynamic Portal Content

Dear All
I am creataing a page on Portal will be used to display advertisements.
Advertisments have many paragraphs. How can I manage the web content of such type on Portal.
Using Webdynpro to fetch text from database is an expensive task.

hi adnan,
Web Content Management in the Enterprise Portal -
The future of traditional Web Content Management (WCM) systems is uncertain. Businesses
are increasingly implementing enterprise portal solutions that are primarily focused
on application and business process integration. However, existing Web Content
Management systems that concentrate on the creation, maintenance and provision of
web-based content, for example for intranet operation, have become established in todays
enterprise. This development presents a new challenge for enterprise IT departments:
These two very separate system worlds must be unified both in design and technology.
Enterprise portals represent a direct advancement for intranets and dynamic websites,
mainly due to the user-specific integration of applications and information in a single,
unified user interface. In order to make a clear distinction, the terms intranet and portal
should be defined:
An intranet provides employees with information using static HTML pages and/or a Web
Content Management System. Access to individual web-based applications from the
intranet is made possible by simple links. Consequently, an intranet is designed mainly
for the purpose of information distribution and is only marginally involved in process optimization.
Since there is no logical connection between the applications, users are forced
to log in separately to various applications with different user registration data. The required
user names and passwords are usually not consistent throughout a company. Furthermore,
roles are not part of intranet design and it is not possible to customize the
user interface (user customizing).
An enterprise portal is a complex integration infrastructure that consolidates application
systems, services and information from a variety of different sources within an enterprise
into a central, unified user interface (e.g. web browser) that is individually adapted for
each employee and accessible from every desktop. Enterprise portal content is individually
adapted for every employee or group; this is made possible by corresponding role
concepts.
Enterprise portals have opened a single point of entry for a variety of different business
applications. So why not simply present the complex content required directly within the
enterprise portal and completely replace existing extranet or intranet solutions? Most
new generation portal software products neglect this concept. The Content Management
they offer out of the box is rudimentary at best. Unfortunately, many IT decision makers
are either partially or completely unaware of this shortcoming.
On the other hand, there are highly sophisticated Web Content Management systems and
products on the market functionalities range from Internet building blocks for creating
simple homepages to adequate workflow integration within the Information Lifecycle.
Moreover, these systems include additional tools for generating navigational structures
as well as editing and authoring tools for managing content on websites. Link management,
approval workflows and access controls for designated areas of the web-based
solution are practically taken for granted. A Web Content Management system delivers
the technologies, tools and methods for creating, managing, storing, preserving and providing
electronic content throughout the entire enterprise. This generally recognized defnition originates from AIIM International (Association for Information and Image Management
International). Unlike document management, which can be described as a database-
supported management system for electronic documents, Web Content Management
encompasses web publishing, publishing intranet or internet pages and provides
structured publication of web-based information.
At first glance, deploying Web Content Management systems allows enterprises to unify
web-based content and application-based information within a single enterprise portal,
regardless of the format in which the information is available.
Some WCM software manufacturers have already taken action and provide specifically
for the SAP NetWeaver Portal comprehensive integration packages that integrate
their high-performance Web Content Management systems in the portal software.
But how do companies manage and supply the content to be published in an enterprise
portal created on the basis of business-oriented portal software? At a time when users
are already confronted with heterogeneous environments in their day-to-day work, every
additional system is simply another burden. Integrating a high-performance, technologically
advanced Web Content Management system in an enterprise portal is problematic
because, to a great extent, both software solutions implement competing concepts and
technologies which must be further explained.
Both systems require their own server infrastructure and rely on their own, completely
proprietary software architecture based on a separate database and/or data storage system.
As a result, additional expenditure is incurred for all of the following aspects:
· Parallel expenditure for hardware
· Parallel expenditure for operation and monitoring
· Parallel expenditure for backup & restore
· Parallel expenditure for security design and implementations
· Parallel expenditure for performance optimization
· Parallel expenditure for administrator training
From the perspective of an enterprise portal infrastructure, a Web Content Management
system is a third-party system which must be integrated via interfaces. Thus, the following
issues must be addressed:
(1) Parallel existence of two navigational structures: a) navigational structures, pages
and roles within the enterprise portal and b) menu items and storage structures
within the external WCM system.
(2) Editors are required to learn how to work with two different tools and user interfaces.
(3) A search function must be developed that can be utilized for both systems; access
rights for both systems must be given special attention here.
(4) Parallel existence of two authorization concepts. Defining access rights in an enterprise
portal is generally possible on the basis of users, groups, and portal roles in
particular. Access rights management in a WCM system has its own administrator interfaces
and authorization objects which need to be aligned.
(5) Parallel workflow concepts: An enterprise portal has application-oriented workflow
procedures that are usually based on the user administration integrated into the portal
(users, roles and groups). A WCM system often uses its own staging concept for
approving web pages based on its own workflow which exists parallel to the portal
workflow.
(6) Parallel user registration data management: Enterprise portals offer powerful features
for user administration which must be used in addition to or in competition
with the WCM system user administration. It makes sense to use a single LDAP interface
for both systems. However, this does not solve the key problem: both systems
have their own administration tools for user management.
(7) Parallel security concepts: Enterprise portals offer very powerful security design concepts
and functions; a WCM system has its own design concepts and these must also
be managed and taken into consideration.
(8) Some external WCM systems generate portal objects (e.g. menu items in portal
roles) via interfaces. Changes to these generated objects are overwritten during
each generation process making it impossible to use all of the functionality of the
portal tools. Only the features that are generated and/or supported by the WCM system
can be fully leveraged.
(9) Parallel concepts for link management: There are different methods for creating and
managing links in both software systems. A particular problem is posed by targets
that affect the role-based navigational structure of the enterprise portal which generally
cannot be conveniently selected as most editors would expect.
(10) Parallel page creation and layout concepts (look & feel): Both systems have their
own concept of performance-optimized page presentation. Similarly, both systems
offer different methods and tools for editing the look & feel of the pages.
Taking the above issues into consideration, serious thought should be given to integrating
an external Web Content Management system in an enterprise portal. From a longterm
perspective and when taking the Total Cost of Ownership into consideration, operating
two IT systems as complex as these parallel to one another is impractical, even if the
WCM system manufacturers offer portal-specific integration packages for their software.
A closer look at these packages shows that many of the interface problems and design
redundancies detailed above will nevertheless continue to persist.
From the authors perspective, every project involving Web Content Management in enterprise
portals should question whether or not the desired editing processes and WCM
requirements could be served with the standard features of the enterprise portal or covered
by an expansion package or implementation and project work. This solution path is
further explained in the following practical example.
Practical example: Web Content Management in the SAP NetWeaver Portal
With its SAP NetWeaver Portal, SAP not only provides the basis for a successful
backend system for business process optimization, but also delivers basic Web Content
Management functionalities. In order to structure the content, the SAP NetWeaver Portal
utilizes a central tool - the Portal Content Studio.
The Portal Content Studio offers a central environment for developing and managing all
types of portal content, such as portlets (iViews), pages, layouts, worksets, roles, and
packages.
Figure 1: Portal Content Studio for the SAP NetWeaver Portal (source: btexx Portal)
The most important object in the Portal Content Catalog is the role, which serves two
purposes: First of all, the role is assigned to users or user groups, achieving the typical
personalization required of an enterprise portal, secondly, the role in the SAP portal defines
the menu structure that is linked to the role at the same time.
A role can be implemented as a hierarchical tree structure with an infinite number of
nested objects. The tree structure is formed by creating folders. Pages or iViews can be
positioned at any level within the hierarchy. There are different types of iViews; typical
examples of iViews are R/3 transactions, eBusiness applications, Internet/intranet applications,
or content-based iViews (HTML content, text, graphics). iViews are typically positioned
and arranged on pages but they can also be independently built into roles.
Within a role, so-called Entry Points must be defined which are then included as a menu
item in both of the top navigation bars of the portal menu. The portal menu is generally
comprised of multiple roles (with corresponding Entry Points). However, the order of the
menu items can be defined (using the Attribute Priority).
Additionally, SAP provides an Internet platform that offers a selection of ready-to-use
portal contents in a general catalog that can be imported into the Portal Content Studio.
SAP calls these out-of- the-box solutions SAP Business Packages. Partners and other
software manufacturers are able to provide solutions and/or interfaces based on this
platform and have them certified by SAP (SAP offers a certification program especially
designed for these solutions). The iView list for the so-called Portal Content Portfolio
(formally iView Studio) includes thousands of iViews.
The SAP Portal Content Portfolio can be accessed here:
https://www.sdn.sap.com/irj/sdn/developerareas/contentportfolio
In many aspects, the tools and capabilities of the Portal Content Studio are comprehensive
and advanced yet they are not sufficient for comprehensive Web Content Management.
First and foremost, the Portal Content Studio supports the establishment of rolebased
navigational structures and the definition of portal pages on which iViews can be
positioned and arranged. This method of content creation is comparatively complex and
not suited for the daily business of an editor, who is typically less involved in changing
content structures and more involved in changing the content elements contained therein
(text, graphics, flash files, links, documents, etc.). Pragmatic methods and simple
mechanisms are desired for the management of this content. The material in the content-
based iViews must be freely definable through simple and intuitive means and editors
should be able to create content themselves.
The SAP Knowledge Management (KM) component is available for storing content and
documents in SAP NetWeaver. The content to be presented can be stored and managed
via a folder structure that must be managed parallel to the Portal Content Directory.
However, in the standard feature set of the SAP NetWeaver Portal, the KM folder where
this content is later to be saved must be defined for every content-based KM iView. An
automatic link between the current role position and the KM location is not created. Simple
shifting between read and edit mode is another feature that is not available in the
standard version despite the fact that this functionality is extremely important for editors.
Despite the multitude of existing functions, the standard SAP NetWeaver Portal offers
insufficient capabilities for comfortable Web Content Management. Editing capabilities for
XML forms, so-called docs iViews, URL-iViews or TREX searches are offered but their use
is anything but intuitive and involves a great deal of administrative expenditure. This
makes a high level of knowledge in building web content within the SAP NetWeaver
Portal a prerequisite. Above all, there are little or no possibilities for using Web Content
Management functionality such as the construction of generic content structures, link
management, multi-language support or a navigational context available from the search
results without the relevant programming or HTML knowledge.
This is where an enhancement from btexx business technologies GmbH, the Business
Package easyWCM for Web Content Management in SAP NetWeaver Portal comes in. It
uses the Portal Content Studio as a central tool yet significantly accelerates editing processes.
It allows content elements to be linked effectively with portal objects that are created
automatically through the use of easyWCM iViews. Every authorized user can create,
publish and edit information.
This Business Package automatically stores the content elements in the KM component
assigned in the navigation structure in the background and makes them available for further
editing on portal pages, greatly simplifying subsequent content management work.
This is why the editor no longer requires technical knowledge of where the content is
stored in the KM. Thanks to easyWCM, both the editor and the end-user work with the
same portal role and costly multiple management of the navigation and content storage
structure is unnecessary. Using the Inplace Editing feature, the editor is able to edit
content directly on the portal pages on which the content is presented and visualized.
The Business Package is based 100% on the SAP NetWeaver Portal and Knowledge
Management Components; no third-party servers or additional software products are required.
The portal server is solely responsible for providing the runtime platform.
A third-party Content Management System may be able to offer a larger selection of features
than easyWCM but it implementing and operating the additional solution will require
a great deal more resources. The easyWCM Business Package for the SAP Net-
Weaver Portal provides Web Content Management simply and effectively while supporting
the following essential requirements:
Complete integration for SAP Portal Content Studio
An editor does not need any tools other than the SAP Portal Content Studio. The desired
navigational structures are provided as SAP portal roles in the SAP Portal Content Studio
- the application of easyWCM iViews is thereby possible anywhere within portal roles,
worksets and pages. The main advantage of this solution is that the editors enter content
in a single environment in which all web content and navigational structures are stored
and administered.
Inplace editing:
End-users and editors work with the same portal roles. Therefore, no separate portal
roles for providing and maintaining the content are required! As an editor, easyWCM
iView offers you the ability to add and work on content components directly within the
portal (Inplace Editing). Furthermore, the editor is able to use SAP KM standard functions
(e.g. authorization assignment, workflow, feedback, rating, etc.) directly within the content
component.
Automatic creation of KM folders
A general standard is that everyone must indicate the respective KM file path in which
the content components are to be stored. This requires a great deal of effort when maintaining
portals with a large number of web content elements. easyWCM automatically
produces the necessary listings with the desired KM authorizations at runtime and simultaneously
activates the desired KM services (life span, manual arrangement, history,
workflow). During shifting or copying processes in the SAP Portal Content Studio, the
elements are automatically moved and copied within the KM!
Preview functionality from Portal Content Studio
A preview function for each form is easily accessible with a single click. It is also possible
to preview items directly from the Portal Content Studio in order to view the complete
portal page, for example. easyWCM iViews were designed in a way that also enables users
to enter and edit content directly from the SAP Portal Content Studio preview function.
Multiple use of content elements
easyWCM iViews may be adjusted in such a way as to allow content to be used more
than once. Using this option, the content is not stored by the role and/or page, but is
linked centrally within the easyWCM iView. The multiple use of content components is
important, for example, if the right column of the portal presentation is exactly the same
for several pages (e.g. for contact data, partners, advertisements, etc.).
Approval workflow
If desired, the SAP KM approval workflow may be activated in order to manage content
elements. Changes to content elements will only be visible after the approval. All XML
forms provided by easyWCM support the SAP KM approval workflow and indicate the
permission status by using traffic lights.
Version management
If desired, the SAP KM version management may be activated in order to manage content
elements. An editor with the proper authorization can specify the portal pages on
which version management should be activated. When version management is activated,
it is possible to replace older content components or to cancel incorrect modifications.
With each change, a new version is automatically stored and documented including the
date and the person who made the change.
Life span
If desired, the SAP KM life span function may be activated in order to manage content
elements. An editor with the proper authorization can specify the portal pages on which
the life span function should be activated. Activating the life span function makes it possible
to publish a content component for a specific period (this is useful for news or
events, for example).
Authorization-based search functionality
The SAP NetWeaver standard component TREX is used for the search function. One of
the key advantages of easyWCM compared to external WCM solutions is that the search
is implemented completely on the basis of the SAP NetWeaver platform and, in particular,
that it is dependent on the authorization status. A separate search machine with its
own user and authorization administration is not required.
Multi-language support
easyWCM automatically detects the language of the editor and stores the content in
separate folders. Folders for content in different languages are created based on the active
portal language.
Ready-to-use forms and pages
easyWCM contains a set of immediately useable portal roles and pages which may be
used for your desired menu structures and page layouts. As such, easyWCM provides the
ability to create and maintain Internet pages without special HTML programming knowledge.
easyWCM also contains more than 30 XML forms based on the XML forms builder
(SAP standard) which can be used for content creation. These XML forms may also be
custom designed to fit your needs.
Personalized user interface
easyWCM determines the user interface depending on portal authorizations of the
user/editor and the corresponding authorizations of the respective KM folders. The
easyWCM package contains different KM layout sets which may be activated via customization,
if desired. Working on content is simple; an editor with the appropriate KM writepermissions
regards
karthik
reward me points if it helps you

How to use an self-made iView in the Portal Content?

Hi everybody,
I followed the instructions to set up a Portal (6.0 SP 2) with the PDK. Now I just wrote a simple "Hello-World" iView and deployed it into the portal server. It worked fine when I clicked to test it in the Java Development Inspector.
But...
In the Portal Content I can not find my self-made iView? How do I get it there? I coudn't find any documentation.
I'd appreciate your help!

In the portal content try to create a new Iview and select the option (create new iview from portal Archive).
After selecting that you will see all the PARs deployed on your server, just select yours and follow on.
Hope that helps.
Thanks
Ankur

ESS application systems creation in Portal content area

Hi ESS experts,
I had struck up in the systems creation part of the ESS implementation in EP7, ECC6.
I have the ESS set up guide by Siddhartha Jain which is just short of details on how to set up the systems for system alias SAP_Webdynpro_XSS, ITS, and back end R/3 system creation in the system and how to test the connections.
Can any one give a detail guide on how to set up the various systems in the Portal content directory to that the Ess application can be launched in the portal?
I had deployed the BP as described in the guide (and guided by the forum members) and all my Jco connections are Green in color. I need to complete the system creation and user creation in the portal and launch the ESS applicaiton in portal.
(Set up the first system on the Portal J2EE server in which the business package has been implemented and assign the system the alias SAP_WebDynpro_XSS.) Here is the step I need help!!!
Please help, and thanks in advance,
Regards

Hi Vinod,
Thanks for the immediate response.
Can you please guide me on the below statement?
>>>Then you need to specify the details of that system and various other properties
Assign the aliases and then test the connectivity. <<<
I do not know which are the system details and other properties that need to be defined to get the connection test passed. I am very new to portal and I need your advise and guidance.
Please help.
Thanks and regards

How to decide the development platform for developing portal content?

Dear Experts
There are several platforms on which we can make
portal contents for SAP Portal.
1)Web Dynpro for Java
2)Web Dynpro for ABAP
3)PDK for .NET
I am trying to find out which of them would be most
efficient while developing system for the client.
It may be that for one who knows Java, Web dynpro for
Java would be efficient and so on.
However, when there is a situation where the developers
need to be trained before the project, which of these
platforms would be the most efficient.
Beside the evaluation based on language of development,
are there some other evaluation based on criteria like the
ease of development, deployment and debugging, cost for the
softwares and hardwares needed for the projects, contents
of the class library, templates provided and so on?
Does anybody have some supporting document that describes
on which circumstances which of these technologies would
be efficient while making systems for the client?
It would be of great help if you could share your insights.
many thanks,
Sudeep

hi sudeep.....
whatever technology, you work in , the output is going to be the same and he ecnd user cannot find out what technology you have used.... ABAP would be better because its growing up fast and many applications are being created using web dynpro abap.
---regards,
alex b justin

Srm-catalog portal content

hi!
does anybody know what is the special content that SRMMDMCAT01_0.sca have?
different iViews?
if i'm implementing srm-portal-mdm-r3 it's necessary?
because i'm not using all the srm catalog, and only installed the mdm portal content, i'll have some problems?
thanx

The purpose of SRM-MDM is to use MDM as the catalog. You would store the data in MDM and SRM will then reference MDM ad-hoc. As part of the implementation, SAP delivers a webdynpro application which is deployed on a Netweaver Java stack, and that's what the user uses to search the catalog. The two applications (iViews) are called SearchUI and AdminUI. If you aren't going to use these, how are you planning on searching the catalog from SRM?

Howto setup portal content folder path?

we want to deploy our par-file (portlet archive) into the portal catalog folder path
/portal_content/other_vendors/every_user/com.name.etc.etc.par
How to setup this path so that the par-file is correctly build and deployed to this path?
The path can be seen with the Portal Content Inspector inside the NetWeaver portal.

Hi,
A par file is not being deployed into the pcd, it is being deployed to the server.
You can then build an iView based on this par anywhere you want within the portal_content folder.
Roy

No preview button or option for all ESS MSS iViews under portal content

Hi All,
We are doing a green field implementation for one of our clients, we have installed ECC 6.0 with EHP5 in R/3 system and SAP Netweaver Portal 7.02 with SP8. We have also deployed suitable ESS MSS business components from service market place.
BP_ERP5ESS 1.41
BPERPESSWDA 1.50
BP_ERP5MSS 1.51
As it is EHP5 in ECC all the Homepage framework, Areas, Sub areas, services are preconfigured for standard ESS MSS business areas.
In Portal side under Portal content - Content Provided by SAP - End User Content - Employee Self Services -
we are not able to preview any of the iViews. can anyone suggest whether what may be wrong...?

Hi Sandeep,
1. Yes we are accessing portal through FQDN
2. IE 6.0
3. I mentioned above, its SAP Netweaver 7.02 with SP8
4. Yes, the user I am using has Super Administrator role
5. There are roles for ESS in ECC
This problem of preview is for other iViews also. I mean other than ESS MSS iViews.
Thanks,
Kalam.

Portal content for STVN 2.1

Hello!
We have recently intalled Nakisa 2.1 on NW CE 7.1.
Now we should import Portal Content in our Portal - accortding to Java Deployment Guide EPA file named com.nakisa.nakisa_portal_contents.epa is expected to be in folder PortalContent under installation folders,
but surprizingly it isn't ther! Moreover, there is no such file anywhere on the server!
We used Installation CD sent to us by SAP, no. 5103811.
So where shoul I get these contents from?
Any suggestion?
Thank you in advance!
Yelena

You are right, the "com.nakisa.nakisa_portal_contents.epa" content should be in
/usr/sap/[system_name]/J00/j2ee/cluster/apps/Nakisa/SuccessionPlanning/PortalContent
folder once you've compeleted the installation.
I would suggest raising this on OSS since that is your official support channel.
The portal content offers some advantages (how it handles systems when moving portal content between environments - DEV, QA, PRD - for example) over just using URL iViews.
Stephen

Portal Content Translation - Transport

Hello
We created some worklist in Portal Content Translation to translate the texts in roles, worksets and iViews from English (source) to German (end user).
Now, we need to transport these worklists to the Test Portal and we tried to follow the steps as described in the help below:
[Performing Language Transports|http://help.sap.com/saphelp_nw70/helpdata/EN/f8/a4c0b28ab7324d835176fdbbb28c3e/frameset.htm]
It did not work:
1) We created a Package with "text_only" property, filled it with the worklists and selected the language to be transported in "Language Transport" menu, but the deployment failed.
2) We created a Package without "text_only" property, filled it with the worklists and did not select any language to be transported. Once imported, the worklists were in the Test Portal, but the translation to german was not in them.
3) We created a Package similar to the one in step 2, but selected the language to be transported in the "Language Transport" menu. The result was the same we had in step 2.
So, what must we do to transport not only the worklists, but also the translations created in the Development Portal?
Thanks in advance, regards!
Jon

Hi,
I'm not sure if I did understand you correctly, but it seems that you want to transport the translation worklist? To transport the translated content, you'll have to do
1. create a translation worklist and assign the PCD objects (iviews, pages, roles)
2. translate the content
3. publish the translated content
4. create a transport package containing the PCD objects translated and transport this package (eg: text_only).
br,
Tobias

Portal Content missing

Hello All,
When I go to Content Administration --> Portal Content, I just see the "Looking..." message but nothing appears. After a couple of minutes "Looking" message ends and nothing is displayed.
I already deployed ESS and MSS Business Packages with SDM but I can't see the content in the Portal Content menu. I can't even see the "default" portal content.
This is my first portal installation and I don't know if I must do something to see the Portal Content in this menu. I'm using Administrator user.
Any help will be appreciated.
Regards
Francisco

Thanks Michael , it works¡
Regards
Francisco

Deployable portal content in NWDI

Hi,
Sorry if this is described in the documentation, I didn't find the right answer.
I have a set of roles, pages, Web Dynpro iViews, a portal desktop, etc. These were manually created in the Portal Content Studio. How do I create a deployable SDA, which will automatically create the same content when deployed? Is it possible to make it out of an EPA? And finally, what kind of project do I have to create in NWDI to store the DC?
Thanks and regards,
Krasimir

Hi,
as far as I know, PortalContentStudio is for creating PortalContent (Roles, Pages, iVies,..) and DeveloperStudio (NWDS) ist for creating Applications (which can be integrated into the portal through some kind of iView).
Besides that these two do not have anything in common. The application an how it is called in some portal are separate (there could be different ways to call the same application).
Why need to make an SDA out of an EPA - EPA's can be easily imported into another portal (transport) as is?

Internationalize WebCenter Portal – Content Presenter

hi,
I tried internationalization of webcenter portal using content presenter.
i followed the following blog solution 1
http://www.ateam-oracle.com/internationalize-webcenter-portal-content-presenter/
I am getting the following error please help
javax.faces.FacesException: oracle.adf.controller.ControllerException: ADFC-10001: cannot instantiate class 'oracle.webcenter.doclib.internal.view.presenter.NLSHelperBean'
I am using latest webcenter extension in jdev 11.1.1.7
thanks,
Chandrasekar M

Hi Daniel,
Previously I have not included CPNLSCustomizations project as ADF JAR Library within myPortal Application.I have included it now.
How to deploy the .MAR customizations? I cannot find any .MAR customizations in the CPNLSCustomizations project.Please help
I am getting the following error now
oracle.mds.core.MetadataNotFoundException: MDS-00013: no metadata found for metadata object "/ridccommon/DataControls.dcx"
at oracle.mds.core.MetadataObject.getBaseMO(MetadataObject.java:1408)
at oracle.mds.core.MDSSession.getBaseMO(MDSSession.java:3874)
at oracle.mds.core.MDSSession.getMetadataObject(MDSSession.java:1589)
at oracle.mds.core.MDSSession.getMetadataObject(MDSSession.java:1525)
Thanks,
Chandrasekar M

How to publish visual composer model to portal content

Dear all,
I need information about how to publish visual composer model to portal content. does any one now???
Regards.

Hi,
after doing deployment the model in the VC will be published in the Portal content.
You can define the path where you want to publish the Model in the Portal under portalk content in
(In VC) Tools->Options->Compiler->Deployment folder(mention the folder name in the portal content).
hope you got my point.
Regards,
Govindu

Portal Content Deployment - History

Similar Messages

Maybe you are looking for