Streamlining the Portal Repository

Hi!
Here is my problem. I need to limit the number of portlets that users see when they customize a page or tab.
What I have done is to create a "Private" folder in the portal repository with security and have moved all of the portlets that users should not see to this folder.
This can be a tedious process if you have a lot of portlets and all new portlets will need to be manually moved to this folder.
Is there a better way to do this?
Thanks,
Kim
Portal Version: 3.0.7.6.2
System: NT 4.0 with Service Pack 6.0
App Server: 9ias
DB: 8.17
null

Kim,
Starting in 3.0.8, when you add a provider it automatically get's put in it's own subfolder. If you can afford to delete your current providers, you can then re-add them to create the subdirectories. However, deleting the providers will break the link to portlets that are already on your pages.
In 3.0.9, which is targeted to a June release, we have a new bulk actions interface that will allow you to copy or move multiple items in a single step. That should solve your problem, if you can wait for that release.
Regards,
Jerry
null

Similar Messages

Users details not getting populated in the portal tables..

Hi,
We have implemented single sign on (SSO) and we do not create users in the portal as user/pwd come from OID.
Now becoz of this the portal tables are not getting populated.I require that all the users of the OID to be populated in the portal tables. How can I do it.I depserately require it.

You can use the function wwsec_api.activate_portal_user to create the shadow records in the portal repository.
Ref. : http://www.oracle.com/technology/products/ias/portal/html/plsqldoc/pldoc1014/wwsec_api.html

Portal Repository

Hello All.
What is the Portal Repository? Do I need a new database to store it or can I put in already exist database.

Hi -
The Portal repository is the schema owned by Portal that contains all the tables and API's used within Portal. Everything produced by Portal is essentially generated dynamically from the database using the programs and data in its repository, and is displayed in a web browser.
You can store it in an existing database (that is the easy answer) but there is quite a bit to it. There needs to be 3 separate physical (or logical) servers - one for the database and portal repository, one for the infrastructure database (including Oracle Internet Directory) and one for the web (application) server. Portal is just one aspect of 9iAS. I've never done the install but it is very difficult with many pitfalls. Read all the release notes and have your ducks in a row before you start.
Art

Web Page Composer: making iViews available in Portal Repository tab

Hello experts.
I'm trying to make some content (banners, images, iviews) for WPC (in SAP EP 7.4) and I cannot find any information how to add an iView to the Portal Repository (see the image). It says 'The contents of this repository are defined by your portal administrator', but I cannot find any documents describing the procedure. Any ideas?
Best regards,
Timur Semenchuk.

Hi,
In portal Content administration ->Portal Content ->Portal users -> WPC Authors ->Area Management role -> Content Editor , set the highlighted properties as shown in screen-shot below.
Regards,
Navya

What is the name of the Portal user detail Table?

Hi.
I using Oracle Portal9iAS 9.0.2.1
1)When administrator register a new user, what is the table that the data is being stored?
2)When a user want to login in the Portal, he/she will be directed to the SSO Login Page?..
-What is the name of the page and where is it been stored?
-I want to customize it to add my company's logo..how can i do that?
Thanks.

Rushdan,
User provisioning information in 9.0.2 is not stored in the portal environment. All user/group information is held in OID only ACL information is held in the Portal repository itself.
There is instructions on creating custom login pages both on Portalcenter.oracle.com and (for java examples) in th e9iAS security guide.

Cannot add Portlets: Portal Repository - Refresh Errors

I cannot add portlets in Portal 3.0.8.
When I click the "Refresh Error" link in the Portal Repository, I get the following error:
PROVIDER[527954]: Oracle Portal Pages PORTLET[886]: TN_ORGAN LANGUAGE: s ERROR: User-Defined Exception
How do I get rid of the error?
null

The way the Refresh works is that for each provider, Oracle9i AS Portal contacts the provider for its list of portlets. It will request the list in each of the installed languages. For database providers, this call is the get_portlet_list API. For web providers, this call is the oracle.portal.provider.v1.Provider.getPortlets java API.
The error you are seeing in the refresh log is being caused by an exception raised in provider=527954,portlet=886,language=s in either the get portlets or get portlet methods. You should check these two methods with Swedish.

KM repository disappears when reboot the portal server

Hi gurus
I develop a repository manager for a database like example from thilo, work fine but when i reboot the portal 7.0 sp 15 and go Portal content->km content-> in root, my repository disappears, i need re-deploy and re-index again
any idea
the only clue is this parto of the log
My repository name is /jdbc
*#1.5 #001143302F1E005E00000499000014D0000464696071349F#1236303659221#com.sapportals.wcm.service.indexmanagement.IndexService#sap.com/irj#com.sapportals.wcm.service.indexmanagement.IndexService#ANON1#0##n/a##4c5c3a8009ef11decd9e001143302f1e#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain###Error while registering for index relevant events: Invalid RID: No repository manager found for prefix: /jdbc - com.sapportals.wcm.repository.ResourceException: Invalid RID: No repository manager found for prefix: /jdbc*
**     at com.sapportals.wcm.repository.ResourceException.fillInStackTrace(ResourceException.java:399)**     at java.lang.Throwable.<init>(Throwable.java:195)
     at java.lang.Exception.<init>(Exception.java:41)
     at com.sapportals.wcm.WcmException.<init>(WcmException.java:78)
     at com.sapportals.wcm.WcmException.<init>(WcmException.java:74)
     at com.sapportals.wcm.util.content.ContentException.<init>(ContentException.java:42)
     at com.sapportals.wcm.repository.ResourceException.<init>(ResourceException.java:249)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getRepositoryManager(CmAdapter.java:511)
     at com.sapportals.wcm.service.indexmanagement.IndexService.registerEvents(IndexService.java:3511)
     at com.sapportals.wcm.service.indexmanagement.IndexService.startUpImpl(IndexService.java:3362)
     at com.sapportals.wcm.service.AbstractService.start(AbstractService.java:167)
     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:247)
     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:109)
     at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:322)
     at com.sapportals.wcm.crt.CrtComponentManager.lookupChildComponent(CrtComponentManager.java:403)
     at com.sapportals.wcm.crt.CrtContainerManager.lookupComponent(CrtContainerManager.java:44)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getService(CmAdapter.java:605)
     at com.sapportals.wcm.repository.manager.taxonomy.TaxonomyRepositoryManager.getIndexService(TaxonomyRepositoryManager.java:805)
     at com.sapportals.wcm.repository.manager.taxonomy.TaxonomyRepositoryManager.startUpImpl(TaxonomyRepositoryManager.java:699)
     at com.sapportals.wcm.repository.manager.AbstractRepositoryManager.start(AbstractRepositoryManager.java:538)
     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:247)
     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:109)
     at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:322)
     at com.sapportals.wcm.crt.CrtComponentManager.lookupChildComponent(CrtComponentManager.java:403)
     at com.sapportals.wcm.crt.CrtContainerManager.lookupComponent(CrtContainerManager.java:44)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getAllRepositoryManagers(CmAdapter.java:430)
     at com.sapportals.wcm.service.urimapper.UriMapperPersistence.init(UriMapperPersistence.java:81)
     at com.sapportals.wcm.service.urimapper.UriMapperService.startUpImpl(UriMapperService.java:366)
     at com.sapportals.wcm.service.AbstractService.start(AbstractService.java:167)
     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:247)
     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:109)
     at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:322)
     at com.sapportals.wcm.crt.CrtComponentManager.lookupChildComponent(CrtComponentManager.java:403)
     at com.sapportals.wcm.crt.CrtContainerManager.lookupComponent(CrtContainerManager.java:44)
     at com.sapportals.wcm.crt.CrtSystemImpl.lookupComponentByUri(CrtSystemImpl.java:131)
     at com.sapportals.wcm.crt.CrtComponentManager.startUp(CrtComponentManager.java:278)
     at com.sapportals.wcm.crt.CrtSystemImpl.startUpComponentManager(CrtSystemImpl.java:166)
     at com.sapportals.wcm.repository.runtime.CmSystem.startUp(CmSystem.java:227)
     at com.sapportals.wcm.repository.runtime.CmSystem.getInstance(CmSystem.java:164)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:974)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:192)
     at com.sapportals.wcm.portal.service.KMServiceImpl.afterInit(KMServiceImpl.java:216)
     at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstanceStep2(PortalServiceItem.java:877)
     at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:1118)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1707)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1662)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.startNonCoreApplications(PortalAppBroker.java:1592)
     at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:422)
     at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
     at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:161)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:361)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:42)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:114)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:394)
     at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:139)
     at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
     at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
#1.5 #001143302F1E005E0000049A000014D000046469607152EA#1236303659237#com.sapportals.wcm.crt.CrtThreadSafeComponentHandler#sap.com/irj#com.sapportals.wcm.crt.CrtThreadSafeComponentHandler#ANON1#0##n/a##4c5c3a8009ef11decd9e001143302f1e#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain###cyclic dependency during startup detected, see stack trace: com.sapportals.wcm.crt.ConstructionException: already starting component: class=com.sapportals.wcm.service.indexmanagement.IndexService, uri=crt://runtime/services/IndexmanagementService
     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToConfigure(CrtThreadSafeComponentHandler.java:196)
     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:108)
     at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:322)
     at com.sapportals.wcm.crt.CrtComponentManager.lookupChildComponent(CrtComponentManager.java:403)
     at com.sapportals.wcm.crt.CrtContainerManager.lookupComponent(CrtContainerManager.java:44)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getService(CmAdapter.java:605)
     at com.sapportals.wcm.service.indexmanagement.IndexService.logToApplog(IndexService.java:3542)
     at com.sapportals.wcm.service.indexmanagement.IndexService.registerEvents(IndexService.java:3516)
     at com.sapportals.wcm.service.indexmanagement.IndexService.startUpImpl(IndexService.java:3362)
     at com.sapportals.wcm.service.AbstractService.start(AbstractService.java:167)
     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:247)
     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:109)
     at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:322)
     at com.sapportals.wcm.crt.CrtComponentManager.lookupChildComponent(CrtComponentManager.java:403)
     at com.sapportals.wcm.crt.CrtContainerManager.lookupComponent(CrtContainerManager.java:44)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getService(CmAdapter.java:605)
     at com.sapportals.wcm.repository.manager.taxonomy.TaxonomyRepositoryManager.getIndexService(TaxonomyRepositoryManager.java:805)
     at com.sapportals.wcm.repository.manager.taxonomy.TaxonomyRepositoryManager.startUpImpl(TaxonomyRepositoryManager.java:699)
     at com.sapportals.wcm.repository.manager.AbstractRepositoryManager.start(AbstractRepositoryManager.java:538)
     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:247)
     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:109)
     at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:322)
     at com.sapportals.wcm.crt.CrtComponentManager.lookupChildComponent(CrtComponentManager.java:403)
     at com.sapportals.wcm.crt.CrtContainerManager.lookupComponent(CrtContainerManager.java:44)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getAllRepositoryManagers(CmAdapter.java:430)
     at com.sapportals.wcm.service.urimapper.UriMapperPersistence.init(UriMapperPersistence.java:81)
     at com.sapportals.wcm.service.urimapper.UriMapperService.startUpImpl(UriMapperService.java:366)
     at com.sapportals.wcm.service.AbstractService.start(AbstractService.java:167)
     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:247)
     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:109)
     at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:322)
     at com.sapportals.wcm.crt.CrtComponentManager.lookupChildComponent(CrtComponentManager.java:403)
     at com.sapportals.wcm.crt.CrtContainerManager.lookupComponent(CrtContainerManager.java:44)
     at com.sapportals.wcm.crt.CrtSystemImpl.lookupComponentByUri(CrtSystemImpl.java:131)
     at com.sapportals.wcm.crt.CrtComponentManager.startUp(CrtComponentManager.java:278)
     at com.sapportals.wcm.crt.CrtSystemImpl.startUpComponentManager(CrtSystemImpl.java:166)
     at com.sapportals.wcm.repository.runtime.CmSystem.startUp(CmSystem.java:227)
     at com.sapportals.wcm.repository.runtime.CmSystem.getInstance(CmSystem.java:164)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:974)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:192)
     at com.sapportals.wcm.portal.service.KMServiceImpl.afterInit(KMServiceImpl.java:216)
     at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstanceStep2(PortalServiceItem.java:877)
     at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:1118)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1707)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1662)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.startNonCoreApplications(PortalAppBroker.java:1592)
     at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:422)
     at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
     at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:161)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:361)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:42)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:114)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:394)
     at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:139)
     at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
     at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
thanks
salvatore

HI
check these links:
https://wiki.sdn.sap.com/wiki/display/KMC/KM%20content%20is%20unavailable%20-%20not%20able%20to%20view%20any%20repositories
https://wiki.sdn.sap.com/wiki/display/KMC/KMCConfigurationLost
SAP Note 1000351
Regards
Shridhar Gowda

Redirecting the DAD entry to a different Portal Repository.

Hi All,
I want to edit the DAD entry to point to a diffent Server. What all things should I do for this? Our Portal environment is as follows:
Server1 : Is Single Sign on Server and had Portal Repository which contains portal applications, content area and pages.
Server2 : Portal Repository which contains portal applications, content area and pages.
There is DAD entry on server1 which points to server2 and the applications on server2 are accessed through this DAD link.
Now I have a full backup of server2 on a different machine(server3). And want the existing DAD (which is pointing from server1 to server2) to point to server3.What all chages should i do for making this work, other than editing the connect string for the corresponding DAD entry. Also I would like to know the DAD entry settings are updated into what all files on the server or tables in the database.It is found that DAD Entries are updated into wdbsvr.app file on Apps server. Does it get updated into any other file on the server. We have Oravle Portal Version 3.0.9.8.3 on AIX.Pls help.
Thanks in advance ,
Tom

Hi Tom,
in effect you have just replicated your database with the portal instance onto server 3.
As such you should only have to update the dad connect string in Server 1 where I presume you are running your only mid tier so that it now has a connect credential pointing to server 3.
I am not too familiar with the 3.0.9.8.3 modplsql, in 9.0.2 you would have to restart the HTTP Server to pick up the DAD edit, in 3.0.9 this may not be necessary.
After doing this you ought to be able to shutdown server 2 and so verify that server 3 is being used.
cheers
Nick

Unable to log into the portal-After Upgrade from NetWeaver 7.0 to 7.3EHP1

Dear Experts,
We have poltal landscape(NW 7.0 Dualstack SPS27) with our customozed themes and par files(Company name,logos and colours)
Recently we upgraded the one of portal from NW 7.0 to NW 7.3EHP1 . Upgrade has been successfilly completed with small issue.
After upgrade all urls are working(/nwa, /sld) except /irj/portal.We know that NW 7.3 EHp1 accepts only ear file i.e we converted the our customized log on par file to ear file through par migration tool and the same was deployed successfully through NWDS 7.3 version.After deploying we are able to access the
/irj/portal url with our customized par(means ear file) without issues,
We are unable to log into the portal after giving the correct user id and password,getting the portal runtime error as foloows.
Portal runtime error
An exception occured while processing your request.Send the exception ID your administrator
Exception id:
see log files for details about this exception
Default.trc log file(/server0/log)
#EP-PIN-PRT#tc~epbc~prtc~api#C00061FD2733006C00000005000056CB#9034950000000004#sap.com/com.sap.portal.runtime.system.hooks#com.sap.portal.prt.
runtime#J2EE_ADMIN#4##43E00B85A79911E380F800000089DCC6#3a483a0fa79911e3903000000089dcc6#3a483a0fa79911e3903000000089dcc6#0#Thread[HTTP Worker
[@900472845],5,Dedicated_Application_Thread]#Plain##
08:14_09/03/14_0005_9034950
[EXCEPTION]
java.lang.RuntimeException: Could not create Resource Repository root folder in PCD
at com.sap.portal.resource.repository.ResourceRepositorySrv.initRepositoryRootContext(ResourceRepositorySrv.java:140)
at com.sap.portal.resource.repository.ResourceRepositorySrv.init(ResourceRepositorySrv.java:93)
at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher$3.service(RequestDispatcherFactory.java:518)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:363)
at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher.init(RequestDispatcherFactory.java:503)
at com.sap.portal.prt.broker.PortalServiceItem.initServiceInstance(PortalServiceItem.java:347)
at com.sap.portal.prt.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:210)
at com.sap.portal.prt.broker.PortalServiceItem.load(PortalServiceItem.java:578)
at com.sap.portal.prt.om.ObjectsManager.createObejctHandle(ObjectsManager.java:234)
at com.sap.portal.prt.om.ObjectsManager.getObjectHandle(ObjectsManager.java:147)
at com.sap.portal.prt.broker.PortalAppBroker.getPortalService(PortalAppBroker.java:498)
at com.sap.portal.prt.service.ServiceManager.getPortalServiceItem(ServiceManager.java:431)
at com.sap.portal.prt.service.ServiceManager.get(ServiceManager.java:220)
at com.sap.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:130)
at com.sap.portal.resource.repository.WebResourceRepositorySrv.init(WebResourceRepositorySrv.java:71)
at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher$3.service(RequestDispatcherFactory.java:518)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:363)
at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher.init(RequestDispatcherFactory.java:503)
at com.sap.portal.prt.broker.PortalServiceItem.initServiceInstance(PortalServiceItem.java:347)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:363)
at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher.init(RequestDispatcherFactory.java:503)
at com.sap.portal.prt.broker.PortalServiceItem.initServiceInstance(PortalServiceItem.java:347)
        at com.sap.portal.prt.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:210)
        at com.sap.portal.prt.broker.PortalServiceItem.load(PortalServiceItem.java:578)
        at com.sap.portal.prt.om.ObjectsManager.createObejctHandle(ObjectsManager.java:234)
        at com.sap.portal.prt.om.ObjectsManager.getObjectHandle(ObjectsManager.java:147)
        at com.sap.portal.prt.broker.PortalAppBroker.getPortalService(PortalAppBroker.java:498)
        at com.sap.portal.prt.service.ServiceManager.getPortalServiceItem(ServiceManager.java:431)
        at com.sap.portal.prt.service.ServiceManager.get(ServiceManager.java:220)
        at com.sap.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:130)
        at com.sap.portal.resource.repository.WebResourceImportService$ResourceImporter.<init>(WebResourceImportService.java:248)
        at com.sap.portal.resource.repository.WebResourceImportService.importApplicationResources(WebResourceImportService.java:172)
        at com.sapportals.portal.navigation.NavigationMimeRepositoryService.loadAllPicsToWRR(NavigationMimeRepositoryService.java:186)
        at com.sapportals.portal.navigation.NavigationMimeRepositoryService.init(NavigationMimeRepositoryService.java:160)
        at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher$3.service(RequestDispatcherFactory.java:518)
        at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:363)
        at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher.init(RequestDispatcherFactory.java:503)
        at com.sap.portal.prt.broker.PortalServiceItem.initServiceInstance(PortalServiceItem.java:347)
        at com.sap.portal.prt.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:210)
        at com.sap.portal.prt.broker.PortalServiceItem.load(PortalServiceItem.java:578)
        at com.sap.portal.prt.om.ObjectsManager.createObejctHandle(ObjectsManager.java:234)
        at com.sap.portal.prt.om.ObjectsManager.getObjectHandle(ObjectsManager.java:147)
        at com.sap.portal.prt.broker.PortalAppBroker.getPortalService(PortalAppBroker.java:498)
        at com.sap.portal.prt.service.ServiceManager.getPortalServiceItem(ServiceManager.java:431)
        at com.sap.portal.prt.service.ServiceManager.get(ServiceManager.java:220)
at com.sap.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:130)
        at com.sap.portal.pcm.iview.admin.PcmIviewCommon.getAdditionalAttributes(PcmIviewCommon.java:358)
        at com.sap.portal.pcm.iview.admin.PcmIviewCommon.initLayers(PcmIviewCommon.java:173)
        at com.sap.portal.pcm.iview.admin.AdminBaseiView.createAttrSetLayersList(AdminBaseiView.java:177)
        at com.sap.portal.pcm.page.admin.AdminBasePage.getCustomImplementation(AdminBasePage.java:76)
        at com.sap.portal.pcm.admin.PcmAdminBase.getImplementation(PcmAdminBase.java:642)
        at com.sapportals.portal.navigation.LightningHelperService.getFrameworkPageAttributesValues(LightningHelperService.java:143)
        at com.sapportals.portal.navigation.LightningHelperService.getFrameworkPageAttributesValues(LightningHelperService.java:171)
        at com.sapportals.portal.navigation.fpm.util.PhaseConfiguration.prepareAttributes(PhaseConfiguration.java:71)
        at com.sapportals.portal.navigation.fpm.util.PhaseConfiguration.storeRelatedAttributesInSharedStorage(PhaseConfiguration.java:35)
        at com.sapportals.portal.navigation.fpm.NavigationFpmListener.doFrameworkPhase(NavigationFpmListener.java:535)
        at com.sapportals.portal.navigation.fpm.NavigationFpmListener.doPhase(NavigationFpmListener.java:122)
        at com.sapportals.portal.pb.fpm.FPMContainer.distributeEvent(FPMContainer.java:63)
        at com.sapportals.portal.pb.fpm.FPM.doDocumentHook(FPM.java:179)
        at com.sapportals.portal.prt.service.document.DocumentHookMulticaster.doDocumentHook(DocumentHookMulticaster.java:100)
        at com.sapportals.portal.prt.service.document.DocumentHookService.doDocumentHook(DocumentHookService.java:119)
        at com.sapportals.portal.prt.service.document.DocumentHookServiceNew.doDocumentHook(DocumentHookServiceNew.java:186)
        at com.sapportals.portal.prt.connection.PortalHook.doDocumentHook(PortalHook.java:665)
        at com.sap.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:183)
        at com.sap.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:107)
        at com.sap.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:141)
        at com.sap.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:206)
        at com.sapportals.portal.navigation.PortalLauncher.doContent(PortalLauncher.java:116)
        at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:213)
        at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:129)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
        at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
        at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
        at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
        at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
        at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
        at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
        at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
        at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
        at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
        at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
        at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
        at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: javax.naming.InvalidNameException: Character not allowed: ':' in 'pcd:resource_repository'
at com.sapportals.portal.pcd.pl.PcdName.checkComponent(PcdName.java:64)
        at com.sapportals.portal.pcd.pl.PcdName.checkNameComponent(PcdName.java:39)
        at com.sapportals.portal.pcd.pl.PcdName.padd(PcdName.java:636)
        at com.sapportals.portal.pcd.pl.PcdName.add(PcdName.java:626)
        at com.sapportals.portal.pcd.gl.util.StringUtils.tokenizeIntoPcdName(StringUtils.java:112)
        at com.sapportals.portal.pcd.pl.PcdName.appendUrlInternal(PcdName.java:408)
        at com.sapportals.portal.pcd.pl.PcdName.<init>(PcdName.java:245)
        at com.sap.portal.resource.repository.ResourceRepositorySrv.initRepositoryRootContext(ResourceRepositorySrv.java:121)
        ... 132 more
1)We are suspecting this issue is related to the theme issue.How to update the theme in the upgraded portal(have a backup of themes)
2)Want to know if we update a theme where it stored at the operating system level(in NW 7.3 EHP1 as well as NW 7.0)
3)Is there any post steps after portal upgrade.
Request you suggest.
Regards
Maruthi

Hi
Refer the SAP Notes
1942399 - Fix usage of unregistered class loader while processing HTTP request in an application being updated or stopped at the same time
1744820 - Migration 7.3 fails while executing migration of pcd_upgrade
1703578 - WPC migration stops during connection creation
1918086 - ERROR: Unable to get iView
Regards
Ram

9.0.2.6 Portal Repository Upgrade Patch problems.

We got some problem with Portal when tryed to apply
9.0.2.6 Upgrade. Could anybody give advice on this issue:
Initial configuration:
Solaris8, Portal 9.0.2.2.14, Oracle 9iAS R2 v.9.0.2.0, RDBMS 9.0.1.3. The infrastructure and midtier work on different SPARC-servers.
Accordingly upgrade procedure we succesfully applied:
a) Infrastructure: 9.0.1.4 Patchset for Oracle RDBMS server, 9.0.2.2 Patchset for OID, Oracle 9iAS SSO-server
migration to 9.0.2.5, 9.0.2.2 Patchset for 9iAS Core.
b) 9.0.1.4 Patchset for Oracle RDBMS server, 9.0.2.2 Patchset for OID, Oracle 9iAS SSO-server migration to 9.0.2.5, 9.0.2.2 Patchset for 9iAS Core, Portal 9.0.2.6
patch.
After this we needed to make just one last step:
Portal 9.0.2.6 Repository Upgrade Patch (2981297) for
changing Portal's repository schemes. It worked but
like a result we got the next errors after patch upgrade
was done:
a) "The following invalid non-Portal objects exist in the Portal Schema: INDEX ABC (the name of portal object), PACKAGE BODY WWMON_REP_REPOSITORY, PACKAGE BODY WWMON_REP_REPOSIT_DTL, PLS-00103: Encountered the symbol "," when expecting one of the following: (-+case mod not null <an identifier>,...) The symbol "null" was substituted for "," to continue.)" See upgtmp/nonportal.log
b) "ERROR: 1 invalid objects remain; ERROR: Failed while updating the new portlet IDS..."
c) "ERROR: ORA-01407: cannot update ("PORTAL"."WWSBR_URL$"."URL") to NULL.
d) Two package body of packages at PORTAL scheme became invalid: WWMON_REP_REPOSITORY, WWMON_REP_REPOSIT_DTL. About 20 package body of packages at PORTAL_DEMO became invalid (It seems like initial portlet ID's disappeared
and except of pportlet_id there is nothing:
Example:
inital statement at body:
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
PORTAL.wwpro_api_invalidation.invalidate_cache(
p_provider_id => p_provider_id,
p_portletid => 1065753336,
p_instance_id => p_reference_path,
p_subscriber_id => PORTAL.wwctx_api.get_subscriber_id ,
p_user => PORTAL.wwctx_api.get_user);
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
after upgrade repository patch:
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
PORTAL.wwpro_api_invalidation.invalidate_cache(
p_provider_id => p_provider_id,
p_portletid => ,
p_instance_id => p_reference_path,
p_subscriber_id => PORTAL.wwctx_api.get_subscriber_id ,
p_user => PORTAL.wwctx_api.get_user);
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Like a result after 9.0.2.6 Portal Repository Upgrade Patch application we lost the possibility to edit user's
profiles at Portal and other nesessary features. It seems
like some portlet ID's just dissapeared from Portal scheme. Could anybody had the same problem with Portal Upgrade 9.0.2.6? Quite possible that we missed some important element at during upgrade but ,really, we didn't wait so unlucky result. Advice something, please...
Regards. Igor.

Igor,
Since you've encountered undocumented errors, your repository upgrade has failed. You'll want to leave the repository as is for troublshooting, if at all possible, and log a TAR with support if you haven't already. They'll ask you to upload your upgrade log file and your upgrade tmp directory.
Regards

How to store custom application data in the Portal

Hello,
Is there a mechanism in the Portal whereby you can put custom application data into persistence and then retrieve it again? I don't want to use the database to store the data. I was hoping there is some API to such a mechanism that will allow you to do this.
Of course, I also mean that I want to persist the data beyond the lifetime of a session - i.e. when the user logs off and comes back later, I want to retrieve the data again. Also, I do not want to use a KM repository, because I do not want to make the application KM-dependent.
Any suggestions would be welcome.
Thanks,
Martin
Message was edited by: Martin Ceronio

Martin,
do you want to store this data on a per-user basis? Then the personalization functionality might be want you want. You could define some additional properties in the portalapp.xml for your component and set its personalization to "no-dialog".
Alternatively, you could store this information as additional attributes of the IUser object. See the following code snippet for details:
IUserMaint mutableUser = UMFactory.getUserFactory().getMutableUser(userName);
mutableUser.setAttribute(NAMESPACE, ATTRIBUTE, "some user-specific data");
mutableUser.save();
(NAMESPACE, ATTRIBUTE being some custom defined String constants that uniquely identify the attribute.
Repost if you need further details.
Regards,
Dominik

An error occurred while accessing the content repository from JDeveloper

Hello,
I'm using Jdeveloper Studio Edition Version 11.1.1.5.0
I created Content Repository conection, following:
RIDC Socket Type: socket
Server hostname: localhost
Content Server Listener Port: 4444
Executing "Teste Connection" result "Success!"
But, trying connect, I receive:
oracle.webcenter.content.internal.model.rc.AbstractRepositoryLogic listFolder
An error occurred while accessing the content repository.
and when I login to my portal and go to administration page, then I am getting this error
"Messages for this page are listed below.
Could not retrieve members from policy store.
and when I go to services tab then i am getting this error "The Documents service is unavailable.
Error contacting the content repository."
Please help me to resolve this problem.
Thank You,
Muhammad Nasir

can anybody help me to resolve this issue please.

EP + BW: Problems with user mapping in the portal

Hi,
I'm trying to connect the portal with the BW by using the report RSPOR_SETUP which is a step-by-step guide. The steps #1 - #11 seems to be ok but my problem is the 12th step, the user mapping/allocation maintenance in the portal.
There is an error emerging (in BW): System failure during call of function module RSWR_RFC_SERVICE_TEST (System failure indicates normally an authentication problem between ABAP and Java)
Another error is emerging by testing the connection in the portal. (System administration u2013 system configuration u2013 system landscape u2013 connection test: the first connection, the SAP Web-AS connection is ok but the second, connection test for connector, is not working.
Especially the connection to the backend system with the defined connector is not working. The output is: u201CConnection failure. Check that single sign on is correct configured.
On step 12 of the step-by-step guide I have to select a user in the portal, relate him to a system alias und maintain his technical username and password for the BW. I think here is the problem. Iu2019m able to select and save a system alias for the user, but Iu2019m not able to save his technical username and password. There is another error emerging (in the portal): u201CVerification of user mapping data for system SAP_BW failed, check credentials for errorsu201D, so Iu2019m not able to save the username and password.
I think thats the my problem. the log file confirms that: "Did not find any existing logon data for principal...." & "No user mapping data available for principal...."
I hope my problem description is understandable.
Any ideas how I can solve the credentials problem to save the username and the password?
Thanks in advance.
Tan
Edited by: Tan Yildiz on Jul 22, 2009 1:26 PM

I could deploy some of the usage types, but there is an error regarding the BI-REPPLAN package. I think it's one of the very last errors that stands between me and a working EP - BI connection. There is a problem with the version. Could you check the log details, to find out more?
Thank you.
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[D:\usr\sap\BIP\JC02\SDM\program\log\sdmcl20090806164716.log]/>
<!PATTERN[sdmcl20090806164716.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Aug 6, 2009 6:47:16 PM   Info: -
Starting validation -
Aug 6, 2009 6:47:16 PM   Info: Prerequisite error handling strategy: OnPrerequisiteErrorSkipDepending
Aug 6, 2009 6:47:16 PM   Info: Update strategy: UpdateLowerOrChangedVersions
Aug 6, 2009 6:47:16 PM   Info: Starting deployment prerequisites:
Aug 6, 2009 6:47:18 PM   Info: Loading selected archives...
Aug 6, 2009 6:47:18 PM   Info: Loading archive 'D:\usr\sap\BIP\JC02\SDM\program\temp\BIREPPLAN04_0-10005889.SCA'
Aug 6, 2009 6:47:21 PM   Info: Selected archives successfully loaded.
Aug 6, 2009 6:47:21 PM   Error: Unresolved dependencies found for the following SDAs:
1.: development component 'bi/plan/helpers/table2'/'sap.com'/'MAIN_NW701P03_C'/'2846642'/'0'
dependency:
       name:     'bi/alv/common'
     vendor:     'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
dependency:
       name:     'bi/alv/ui'
     vendor:     'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
Deployment will be aborted.
Aug 6, 2009 6:47:21 PM   Error: No Software Component Archive (SCA) or Software Delivery Archive (SDA) selected. Select at least one.
Deployment will be aborted.
Aug 6, 2009 6:47:21 PM   Error: Prerequisites were aborted.
Aug 6, 2009 6:47:22 PM   Error: Error while creating deployment actions. No Software Component Archive (SCA) or Software Delivery Archive (SDA) selected. Select at least one.
Deployment will be aborted.
Aug 6, 2009 6:47:23 PM   Info: -
Ending validation -

Starting and Stopping the Portal

Hi all
   After deploying my PAR, I am restarting the whole <b>SAP Instance</b> in the Server.
1. Is this the right way ???
2. Is there any other easy way to restart/stop the PORTAL alone instead of touching the SAP Instance???
Thanks
Kay

Hi Kay,
You are right about custom login changes.But Normaly if you develop portal application and upload the PAr file ,you do not have to restart the instance.Portal runtime takes care of droping the existing copy of the PAR or replacing with newer version.
This is what i get from help
Portal Archive Files Deployment Cycle
Use
The deployment procedure for a Portal Archive (PAR) file consists of two steps:
Uploading the PAR file into the application repository
Notifying all Portal Runtime (PRT) nodes that a new version of the application is available
Activities
Uploading a PAR File to the Application Repository
There is only one application repository and all PRT nodes and PAR files on the J2EE Engine cluster share the same content. The PAR upload procedure stores the whole archive in the underlying persistence layer. It also extracts all the information that requires fast access at runtime from the portalapp.xml.
Modifying PRT Nodes
Once the upload to the application repository is completed, the upload process notifies all PRT nodes. This step updates thelocal deployment of the portal application on each server. The update of the local deployment requires runtime deployment capabilities, and that is why all portal applications can be released. A PRT node:
·        Checks if the application is already loaded and drops the corresponding instance.
This step also checks and drops all entities (applications, components and services) that depend on the current application.
·        Starts the deployment process.
This process gets the PAR file from the repository and updates the local deployment by expanding the archive content.
·        Restarts all portal applications that have been dropped.
The main purpose of the local deployment is to improve performance at runtime by providing fast access to classes and to portal application resources. The local deployment avoids additional round trips to the application repository and, in that sense, must be considered as a cache for portal applications.
Deployment Policy
The local deployment is done using the DeploymentPolicy property declared in the portalapp.xml file:
·        If this property is set to 5.0
The deployment is backwards compatible with the EP50 version of the portal. The old folder is not removed and the deployment process simply overrides the folder with the new content.
·        If the DeploymentPolicy property is missing
A regular deployment is performed; the old deployment folder is removed and then replaced by the new one.
The deployment logic assumes that the application does not store any configuration locally; everything must be stored in the repository.
For more information about the DeploymentPolicy property, see Application-Config Element Properties.

How to make use of the portal service "xsltransform"

Hi all,
I am using EP5 SP4 and is trying to create a component to do xml transformation by using the portal service "xsltransform". However when I run the code (which is reference to an example on web), the following error occured:
javax.naming.NotContextException: broker should be a Context
     at com.sapportals.portal.prt.repository.AbstractHierarchicalContext.lookup(AbstractHierarchicalContext.java:139)
     at com.sapportals.portal.prt.repository.AbstractHierarchicalContext.lookup(AbstractHierarchicalContext.java:140)
     at com.sapportals.portal.prt.repository.AbstractHierarchicalContext.lookup(AbstractHierarchicalContext.java:74)
     at javax.naming.InitialContext.lookup(InitialContext.java:345)
     at com.mk.kmbrowserid.MkKmBrowseRID$MkKmBrowseRIDDynPage.doProcessBeforeOutput(MkKmBrowseRID.java:167)
Here is my code:
Hashtable env = new Hashtable();
     env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sapportals.portal.prt.registry.PortalRegistryFactory");
     InitialContext context = new InitialContext(env);
     IXSLTransformService xslTransService = (IXSLTransformService) context.lookup("/broker/services/"+IXSLTransformService.KEY);
     //retrieve the xsl file and put into string
     String line;
     StringBuffer styleSheet = new StringBuffer();
     IResourceContext resourceContext = new ResourceContext(myUser);
     IResourceFactory resFactory = ResourceFactory.getInstance();
Where the problem is occured in line 167 "IXSLTransformService xslTransService = (IXSLTransformService) context.lookup("/broker/services/"+IXSLTransformService.KEY);"
Do any one know how to solve this problem? And setting / config should be done before the service "xsltransform" can be used?
Thanks
Sam

hi
I need an example please....
did any one use that FM
Regards

Streamlining the Portal Repository

Similar Messages

Maybe you are looking for