Questions in topic: "syndication"https://developer.ibm.com/answers/questions/topics/single/170782.html
The latest questions for the topic "syndication"How to resolve "No space left on device" error during syndication?https://developer.ibm.com/answers/questions/482169/how-to-resolve-no-space-left-on-device-error-durin.html
I am syndicating WCM content from my Portal 8.0 environment to my Portal 8.5 environment.
Syndication fails with the following error in the browser: <br>
java.io.IOException: No space left on device
How do I resolve this error?digexpwcmsyndicationspaceMon, 26 Nov 2018 19:26:43 GMTDavid A BatresFirst time syndication from Virtual Portal to Virtual Portal is failing with IWKWC0004I: Code #405, phrase: Unrecognized senderhttps://developer.ibm.com/answers/questions/474553/first-time-syndication-from-virtual-portal-to-virt.html
On Portal 8.5 CF15, set up syndication from Virtual Portal to to Virtual Portal.<br>
The Virtual Portals are set up to use the VP context.<br>
The syndicator URL and Subscriber URL are correct in both the UI and in the trace logs. <br>
But syndicator is not able to access the subscriber.
In the syndication trace logs we see:
The syndicator attempt to perform a HTTP post to
AbstractReque 3 sendRequest() - Sending request with url
[http://<hostname>:<port>/<context>/wcm/connect/<VPcontext>?MOD=Subs:]
and requestMsg com.aptrix.syndication.messaging.RequestMsg@ad33acbb (retries=0)
In the same syndication logs we see the subscriber process starting <br>
(I would expect to see this in the subscriber side trace logs)
[<Timestampe> EDT] <thread> EJSWebCollabo > preInvoke Entry
IWKWC0004I: Code #405, phrase: Unrecognized sender,
detail: Failed to retrieve subscriber.
(Cause: com.ibm.workplace.wcm.services.content.ItemNotFoundException:
Failed to find controllable: {<Subscriber UUID>, com.aptrix.pluto.control.Controllable},
in vp instance: <VP ID>, with context path <VP context>, and hostname: null ),
Cause: com.aptrix.syndication.data.InvalidSubscriberException:
Why is the subscriber process being invoked on the syndicator machine? <br>
Why is it unable to find the subscriber controllable UUID.portaldigexphow-tosyndicationWed, 10 Oct 2018 15:19:26 GMTMRPooleAssign update syndicator to specific usershttps://developer.ibm.com/answers/questions/474236/assign-update-syndicator-to-specific-users.html
I am using WebSphere Portal 8.5 - CF12 and I need to give access to specific users to perform update syndicator. Is it possible?
I assigned the following permissions but still not working:
Editor permission on the web content libraries: Administration -> Portal Content -> Web Content Libraries -> set permissions on each library
Administrator Permissions on Syndicators Page: Resource Permissions -> Pages -> Administration -> WebSphere Portal -> Portal Content -> Syndicators
Administrator Permissions on Web Content Syndicators Portlet: Resource Permissions -> Portlets -> Web Content Syndicators
Only after i added Administrator Permission on "Set Access on Root" in Web Content Libraries the update syndicator and edit syndicator buttons appeared for all the syndications.
I don't want to give edit syndication access to the user only update syndication. Please advise if there is any possibility.portalwcmaccessusersyndicationroleassigningWed, 10 Oct 2018 07:20:25 GMTMuhammad-KhanInline editing fails when add in Nav result design(Nav component is rendered through JSP because its not getting path where it needs to loop files)https://developer.ibm.com/answers/questions/467087/inline-editing-fails-when-add-in-nav-result-design.html
I did this in two ways
Reason for hardcoding is because i was not getting the dialog box after adding authoring tool for read,edit and delete
1) If i hardcode the script and just change the content IDs, its working only on that page where i've hardcoded
Below is the URL
![alt text][1]
- Looking into above url, i dont know where the heck ns_Z7_L2C2HG01N80TB0Q4K0I7FN10B6 in javascript coming from ? Does anybody knows this ?
-Inline edit doesnt work after drag and drop
2) The other is normal, i've added authoring tool where i've added read,edit and delete. But its not opening the dialog box but instead taking it to the WCM after click
![alt text][2]
![alt text][3]
Taking to the WCM after click ![alt text][4]
...
I've added this authoring tool in the nav design where i'm rendering that Nav using JSP
![alt text][5]
[1]: /answers/storage/temp/23882-5.png
[2]: /answers/storage/temp/23878-1.png
[3]: /answers/storage/temp/23879-2.png
[4]: /answers/storage/temp/23880-3.png
[5]: /answers/storage/temp/23881-4.pngportalsyndicationvirtual portalstaging-to-productioneditinginlineportalsiteMon, 27 Aug 2018 21:40:59 GMTsimmyjohnIs it possible to syndicate part of WCM library?https://developer.ibm.com/answers/questions/464848/is-it-possible-to-syndicate-part-of-wcm-library.html
There is a requirement to syndicate only few items in a library so that only those items are seen on the rendering server. Is there a way to achieve this?wcmsyndicationWed, 15 Aug 2018 15:31:04 GMTMishaSShaikhPerforming InitialContext lookup of Portal / WCM service using wsadminhttps://developer.ibm.com/answers/questions/458906/performing-initialcontext-lookup-of-portal-wcm-ser.html
I'm working on a Jython script for wsadmin that can be scheduled in Cron to update a WCM syndicator. The problem arises when doing the context lookup for "portal:service/wcm/WcmSyndicationService". The resulting error is "NamingManager.getURLContext cannot find the factory for this scheme: portal". I'm wondering if the issue could be the initial context factory being used but I couldn't find a class documented for use with Portal / WCM. I thought the other possibility may just be that the "portal" scheme simply isn't accessible through wsadmin even though I'm connecting to the Portal server and not the Dmgr.
I verified that the service is enabled in the services.properties file according to the API [documentation][1]:
# WCM Syndication Service
com.ibm.workplace.wcm.api.WcmSyndicationService = com.ibm.workplace.wcm.api.WcmSyndicationServiceImpl
com.ibm.workplace.wcm.api.SyndicationService = com.ibm.workplace.wcm.api.SyndicationServiceImpl
SAMPLE CODE:
set the context values in a hashtable
env = Hashtable()
env.put(Context.SECURITY_PRINCIPAL, sys.argv[1])
env.put(Context.SECURITY_CREDENTIALS, sys.argv[2])
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.ibm.websphere.naming.WsnInitialContextFactory")
# using Portal server hostname and BOOTSTRAP_ADDRESS port
env.put(Context.PROVIDER_URL, "corbaloc:iiop:prtdev.corp.fin:10052")
# get the initial context (this works fine)
ctx = InitialContext(env)
# try lookup of WcmSyndicationService (this fails)
syndicationService = WcmSyndicationService(ctx.lookup("portal:service/wcm/WcmSyndicationService"))
OUTPUT:
WASX7209I: Connected to process "PortalCluster_prtdevNode" on node prtdevNode using SOAP connector; The type of process is: ManagedProcess
WASX7017E: Exception received while running file "/opt/scripts/python/Modules/resources/runSyndicator.py"; exception information: com.ibm.bsf.BSFException: exception from Jython:
Traceback (innermost last):
File "<string>", line 42, in ?
javax.naming.ConfigurationException: NamingManager.getURLContext cannot find the factory for this scheme: portal
[1]: ftp://public.dhe.ibm.com/software/websphere/portal/javadoc/vrm/850/api_docs/com/ibm/workplace/wcm/api/WcmSyndicationService.htmlwsadminsyndicationwebsphere portal 8.5jythonTue, 17 Jul 2018 14:54:48 GMTStuartSharpUpgrade of Portal 8.5 CF04 to 8.5 CF15 fails with WCM Not Available error.https://developer.ibm.com/answers/questions/455079/upgrade-of-portal-85-cf04-to-85-cf15-fails-with-wc.html
We are running running Portal 8.5 with CF 04 and tried to upgrade to CF15. Environment is a cluster. The Portal binary Install on primary of CF04 completed successfully. But when running applyCF command it fails.
The ConfigEngine log shows:
action-remove-xmlaccess-removeSIFeaturePack-components/wp.ctc.nswiz.apppage.virtual:
[2018-05-11 12:49:34.395] Target started: action-remove-xmlaccess-removeSIFeaturePack-components/wp.ctc.nswiz.apppage.virtual
[echo] wplc-wait-for-sync-to-complete: maxTimeToWait set to: 30
[echo] wplc-wait-for-sync-to-complete: maxAppTimeToWait set to: 5
[antcall] executing target: si-wait-for-sync-to-complete
si-wait-for-sync-to-complete:
[2018-05-11 12:49:34.408] Target started: si-wait-for-sync-to-complete
[wplc-node-autosync-check-state] Task parameters:
[wplc-node-autosync-check-state] Global attributes:
[wplc-node-autosync-check-state] cell="dmgrCell01"
[wplc-node-autosync-check-state] engineinstalllocation="/app/IBM/WebSphere/wp_profile/ConfigEngine"
[wplcnode-autosync-check-state] enginerootdir="/app/IBM/WebSphere/ConfigEngine"
[wplc-node-autosync-check-state] pathseparator=":"
[wplc-node-autosync-check-state] osarch="amd64"
[wplc-node-autosync-check-state] node="sa02webapp01Node"
[wplc-node-autosync-check-state] server="WebSphere_Portal"
[wplc-node-autosync-check-state] CellName is dmgrCell01
[wplc-node-autosync-check-state] NodeName is sa02webapp01Node
[wlc-node-autosync-check-state] ServerName is WebSphere_Portal
[wplc-node-autosync-check-state] Server/Node are part of Cluster PortalCluster Will scope to Cluster
[wplc-node-autosync-check-state] Server and node are part of cluster. Using cluster scope is Cell=dmgrCell01:ServerCluster=PortalCluster
[wplc-node-autosync-check-state] cluster name is PortalCluster
[wplc-node-autosync-check-state] ObjectName queryName = WebSphere:type=NodeSync,process=nodeagent,node=sa02webapp01Node,*
[wplc-node-autosync-check-state] ObjectName = WebSphere:name=nodeSync,process=nodeagent,platform=common,node=sa02webapp01Node,diagnosticProvider=true,version=8.5.5.13,type=NodeSync,mbeanIdentifier=nodeSync,cell=dmgrCell01,spec=1.0
[wplc-node-autosync-check-state] Detected autosync = false
[wplc-node-autosync-check-state] Status = Complete
[echo] EJPCE0070I: auto sync appears to be turned off, therefore, After deployment has completed, you will need to perform a manual sync of all nodes in the cluster
[2018-05-11 12:49:34.622] Target finished: si-wait-for-sync-to-complete
[copy] Copying 1 file to /app/IBM/WebSphere/wp_profile/ConfigEngine/config/work/components/wp.ctc.nswiz.apppage.virtual
[xmlaccess] EJPXB0006I: Connecting to URL http://localhost:10039/wps/config/
[xmlaccess] EJPXB0002I: Reading input file /app/IBM/WebSphere/wp_profile/ConfigEngine/config/work/components/wp.ctc.nswiz.apppage.virtual/pageRemove.xml
[xmlaccess]
[xmlaccess] <!-- IBM WebSphere Portal/8.5 build 20171201-1253 exported on Fri May 11 12:49:39 AST 2018 from sa02webapp01/192.168.179.21 virtual portal: none (default virtual portal) -->
[xmlaccess]
[xmlaccess]
[xmlaccess] EJPXA0001E: An error occurred while processing the XML configuration request.
[xmlaccess] IBM Web Content Manager is not available.
[xmlaccess]
[xmlaccess] com.ibm.wps.command.xml.XmlCommandException: EJPXA0001E: An error occurred while processing the XML configuration request.
[xmlaccess] at com.ibm.wps.command.xml.items.ContentNodeItem$XmlPageAdministrationEventListener.deleted(ContentNodeItem.java:2760)
[xmlaccess] at com.ibm.wps.command.xml.items.ContentNodeItem.delete(ContentNodeItem.java:2088)
Looking at SystemOut.log it shows this corresponding error:
[5/11/18 12:49:39:250 AST] 00000119 Engine E com.ibm.wps.command.xml.Engine processSax EJPFB0002E: Exception occurred.
com.ibm.wps.command.xml.XmlCommandException: EJPXA0001E: An error occurred while processing the XML configuration request.
at com.ibm.wps.command.xml.items.ContentNodeItem$XmlPageAdministrationEventListener.deleted(ContentNodeItem.java:2760)
at com.ibm.wps.command.xml.items.ContentNodeItem.delete(ContentNodeItem.java:2088)
at com.ibm.wps.command.xml.ConfigItem.doUpdate(ConfigItem.java:558)
at com.ibm.wps.command.xml.UpdateEngine.processItem(UpdateEngine.java:210)
at com.ibm.wps.command.xml.UpdateEngine.updateTopLevelItem(UpdateEngine.java:165)
at com.ibm.wps.command.xml.XmlAccessHandler.fillObjectModel(XmlAccessHandler.java:332)
at com.ibm.wps.command.xml.XmlAccessHandler.endElement(XmlAccessHandler.java:210)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
Caused by: com.ibm.wps.wcm.events.xmlaccess.PageModificationListenerModelException: IBM Web Content Manager is not available.
at com.ibm.wps.wcm.events.xmlaccess.ManagedPagesXmlAccessPageModificationListener$3.run(ManagedPagesXmlAccessPageModificationListener.java:355)
at com.ibm.wps.ac.impl.UnrestrictedAccessImpl.run(UnrestrictedAccessImpl.java:84)
at com.ibm.wps.command.ac.ExecuteUnrestrictedCommand.execute(ExecuteUnrestrictedCommand.java:90)
at com.ibm.wps.wcm.events.xmlaccess.ManagedPagesXmlAccessPageModificationListener.runUnrestricted(ManagedPagesXmlAccessPageModificationListener.java:993)
at com.ibm.wps.wcm.events.xmlaccess.ManagedPagesXmlAccessPageModificationListener.deleted(ManagedPagesXmlAccessPageModificationListener.java:311)
at com.ibm.wps.command.xml.items.ContentNodeItem$XmlAccessPageModificationListenerDispatcher.deleted(ContentNodeItem.java:3527)
at com.ibm.wps.command.xml.items.ContentNodeItem$XmlPageAdministrationEventListener$2.call(ContentNodeItem.java:2753)
at com.ibm.wps.services.wcm.SynchronizationEventControlServiceImpl.executeWithoutPortalUpdates(SynchronizationEventControlServiceImpl.java:69)
at com.ibm.wps.command.xml.items.ContentNodeItem$XmlPageAdministrationEventListener.deleted(ContentNodeItem.java:2748)
... 68 more
Caused by: com.ibm.workplace.wcm.api.exceptions.ServiceNotAvailableException: IBM Web Content Manager is not available.
at com.ibm.workplace.wcm.api.WCM_Repository.getSystemWorkspace_aroundBody8(WCM_Repository.java:376)
at com.ibm.workplace.wcm.api.WCM_Repository$AjcClosure9.run(WCM_Repository.java:1)
at com.ibm.workplace.wcm.api.WCMAPIWorkspaceAspect.ajc$around$com_ibm_workplace_wcm_api_WCMAPIWorkspaceAspect$1$77189ab8proceed(WCMAPIWorkspaceAspect.aj:1)
at com.ibm.workplace.wcm.api.WCMAPIWorkspaceAspect$WCMAPIWorkspaceAspect$1.run(WCMAPIWorkspaceAspect.aj:243)
at com.ibm.workplace.wcm.api.WCMAPIWorkspaceAspect.ajc$around$com_ibm_workplace_wcm_api_WCMAPIWorkspaceAspect$1$77189ab8(WCMAPIWorkspaceAspect.aj:294)
at com.ibm.workplace.wcm.api.WCM_Repository.getSystemWorkspace(WCM_Repository.java:334)digexpupgradeportal 8.5syndicationapplycfmanaged pagesMon, 25 Jun 2018 08:06:59 GMTAlexPahlCreating a new Page using a previosley used Unique Name does not get Syndicated.https://developer.ibm.com/answers/questions/455073/creating-a-new-page-using-a-previosley-used-unique.html
We are using Portal 8.4 CF15
We have configured manual syndication of the Portal Site Library. Sometimes we create a copy of an existing page, in Manage Pages by doing the following:
Renaming the Unique Name of the existing page that is already syndicated.
Create a new page with same name as the existing page and same Unique name as it was assigned to the existing page before re-naming.
But then the syndication does not pick up this new page, and only the old page with the - renamed Unique Name is updated on subscriber.
These are the exact steps to duplicate the issue:
1. Create a new page with name e.g. test and unique name utest on the Syndicator.
2. Run and update syndication - Now you see new page on Subscriber.
3. Rename the Unique Name of this page to e.g. from utest to utestOld on Syndicator.
4. Create a new page with same name (test) and same uName as set on original page before the rename (utest), on Syndicator.
5. Run update Syndication.
6. Now check the subscriber, you will only see the old test page with renamed unique name (utestOld) But the new page with the 'original' unique name is not there.
7. Now edit the page, e.g. add a portlet and run syndication again, Now the page appears on subscriber after syndication.
Issue seem to only occur when using manual Syndication.digexpportal 8.5syndicationmanaged pagesMon, 25 Jun 2018 07:43:29 GMTAlexPahlWhy don't I see the WCM library or any content items show up on the subscriber while syndication is actively running?https://developer.ibm.com/answers/questions/452414/why-dont-i-see-the-wcm-library-or-any-content-item.html
I am syndicating all items and versions from my Portal 8.0 environment to my Portal 9.0 environment (about 600GB of size in the database). I have found the following resources to monitor syndication status.
<br><br>
&#49;. Using the syndication portlet as described in this dWAnswers link:<br>
https://developer.ibm.com/answers/questions/366748/monitor-syndication-progress.html
and the knowledge center:<br>
https://www.ibm.com/support/knowledgecenter/SSHRKX_8.5.0/help/panel_help/wcm_syndication_monitoring.html
&#50;. Check if the subscriber temp directory is growing or shrinking.<br>
wp_profile/PortalServer/wcm/ilwwcm/system/subscriber
&#51;. Creating a custom WCM JSP to check the status.<br>
https://developer.ibm.com/answers/questions/301930/sample-code-using-wcm-api-jsp-to-monitor-syndicati.html
&#52;. Checking for syndication messages in the SystemOut log.<br>
https://developer.ibm.com/answers/questions/398237/where-can-i-find-event-logging-to-monitor-the-synd.html
<br><br>
I have even turned on syndication traces:<br>
com.aptrix.deployment.&#42;=all:com.aptrix.syndication.&#42;=all
<br><br>
All of these monitoring options indidcate that syndication is actively running, but I dont' see the libraries or any content show up on the subscriber.
The process has been running for a few days now, but there is no indication in the authoring UI that any content has syndicated yet.
I would have at least expected the library to be created and a few content items to show up in the subscriber after a few hours.
Why don't I see the WCM library or any content items show up on the subscriber while syndication is actively running?portaldigexpwcmmonitorsyndicationstatusFri, 08 Jun 2018 19:43:52 GMTDavid A BatresHow do I prevent draft WCM content visible in Portal live site?https://developer.ibm.com/answers/questions/452383/how-do-i-prevent-draft-wcm-content-visible-in-port.html
I have an authoring and rendering environment where I only syndicate published content from authoring to rendering. When content authors publish content, content is syndicated and visible on live site. However, if a content author in authoring takes a published content and does More -> Previous Stage, the published content becomes draft in authoring. Since only published content syndicates to rendering, the change does not syndicate and the content is still published in rendering. How can I prevent draft content to be visible on live site?portaldigexpwcmsyndicationpublishdraftFri, 08 Jun 2018 16:37:44 GMTOscarIHernandezWhy do I get Error 404: EJCBD0006E when clicking on 'Subscriber Now' to create a syndication pair?https://developer.ibm.com/answers/questions/425089/why-do-i-get-error-404-ejcbd0006e-when-clicking-on.html
In WebSphere Portal, I'm using the Portal Administration UI function to create a syndication pair. Upon clicking on 'Subscribe Now' I get the error "Error 404: EJCBD0006E: The resolution of a URI failed. Refer to SystemOut.log for more detailed information"portaldigexpsyndicationWed, 17 Jan 2018 15:31:48 GMTJoshua_Tsaii have Base portal and virtual portal, i'm trying to import an image from one portal and embed into another in IBM websphere portal Web content management ? is that possible in web content management ?https://developer.ibm.com/answers/questions/414503/ill-be-making-two-virtual-portal-and-im-trying-to.html
i have Base portal and virtual portal, i'm trying to import an image from one portal and embed into another in IBM websphere portal Web content management ? is that possible in web content management ?syndicationvirtual portalstaging-to-productionwcm apiweb content managerwcm-libraryweb contentportalsiteWed, 22 Nov 2017 04:28:14 GMTsimmyjohnDoes WCM Syndication depend on WebDav PropFind method?https://developer.ibm.com/answers/questions/409403/does-wcm-syndication-depend-on-webdav-propfind-met.html
In Websphere Portal, does WCM syndication use the WebDav PropFind method?
Will blocking this method at the network prevent syndication from being successful?portaldigexpsyndicationThu, 26 Oct 2017 15:52:24 GMTJoshua_TsaiPotal 8.5 syndication is failing on CatalogRetrieverTask with Error: 400https://developer.ibm.com/answers/questions/406293/potal-85-syndication-is-failing-on-catalogretrieve.html
On WebSphere Portal 8.5 environment, WCM Syndication fails with following error:
PackageConsum E Unexpected exception thrown while updating subscription:
[IceId: d9ad6b56-7f6d-454d-986c-221b258c7671 Current State: ICE-INITIAL], exception:
com.ibm.workplace.wcm.services.WCMServiceRuntimeException: code: 400
at com.aptrix.syndication.business.subscriber.CatalogRetrieverTask.getSourceCatalog
at com.aptrix.syndication.business.subscriber.CatalogRetrieverTask.process
at com.aptrix.syndication.business.subscriber.PackageConsumerTask.processPackage
Confirmed that the Credential Vault information is current and correct. <br>
Confirmed that HTTP Basic Authentication TAI is enabled properly on both Synd and Sub.
Why are we seeing an error code 400 on CatalogRetrieverTask?portaldigexpwcmsyndicationWed, 11 Oct 2017 13:57:08 GMTMRPooleCan not delete syndication pairhttps://developer.ibm.com/answers/questions/386061/can-not-delete-syndication-pair.html
In a case, customer could not delete syndication pair. We found following exception in backend SystemOut.log
[7/11/17 14:51:21:811 NZST] 0000003f AbstractComma E <Null Message>
java.lang.NoSuchMethodError: com/ibm/icm/da/portable/common/WSLocks.collectiveBatchDeleteLock(Lcom/ibm/icm/da/portable/data/ProcessLinks$DeleteData;)V
at com.ibm.icm.da.portable.data.ProcessLinks.collectiveBatchRemoveLink(ProcessLinks.java:826)
at com.ibm.icm.da.portable.data.ProcessLinks.processLinks(ProcessLinks.java:1622)
at com.ibm.icm.da.portable.data.DataManager.processLinks(DataManager.java:579)
at com.ibm.icm.ci.data.impl.PathService._executeProcessLinkAction(PathService.java:310)
at com.ibm.icm.ci.data.impl.PathService._processPathList(PathService.java:294)
at com.ibm.icm.ci.data.impl.PathService.removeByParentChildPair(PathService.java:264)
at com.ibm.icm.jcr.NodeImpl.save(NodeImpl.java:2545)
at com.ibm.icm.jcr.NodeImpl.save(NodeImpl.java:2450)
at com.ibm.icm.jcr.WorkspaceImpl.save(WorkspaceImpl.java:2785)
at com.ibm.icm.jcr.WorkspaceImpl.save(WorkspaceImpl.java:2774)
at com.ibm.workplace.wcm.services.transaction.steps.repository.SaveWorkspace.execute(SaveWorkspace.java:106)
at com.ibm.workplace.wcm.services.transaction.CompositeTransactionStep.execute(CompositeTransactionStep.java:143)
at com.ibm.workplace.wcm.services.transaction.steps.repository.RepositoryRemove.execute(RepositoryRemove.java:179)
at com.ibm.workplace.wcm.services.transaction.TxUnitOfWork$1.call(TxUnitOfWork.java:117)
at com.ibm.workplace.wcm.util.transaction.DefaultTransactionManager.doCall(DefaultTransactionManager.java:323)
at com.ibm.workplace.wcm.util.transaction.DefaultTransactionManager.doCall(DefaultTransactionManager.java:238)
at com.ibm.workplace.wcm.util.transaction.DefaultTransactionManager.call(DefaultTransactionManager.java:116)
at com.ibm.workplace.wcm.services.transaction.TxUnitOfWork.run(TxUnitOfWork.java:172)
at com.ibm.workplace.wcm.services.content.ContentServiceImpl.remove(ContentServiceImpl.java:2169)
at com.ibm.workplace.wcm.services.content.ContentServiceImpl.remove(ContentServiceImpl.java:2065)
at com.ibm.workplace.wcm.app.ui.admin.syndicator.MainSyndicatorModel.deleteItem(MainSyndicatorModel.java:280)
at com.ibm.workplace.wcm.app.ui.admin.core.command.DeleteAdminObjectCommand.doCommand(DeleteAdminObjectCommand.java:122)
at com.ibm.workplace.wcm.app.ui.portlet.command.AbstractCommand.commandPerformed(AbstractCommand.java:217)portalwcmsyndicationWed, 12 Jul 2017 00:56:21 GMTGeorge HuangSyndication failing with error IWKSY1072E Could not determine the root cause of this failure. An unexpected error has occurred while updating this item. Contact your Administratorhttps://developer.ibm.com/answers/questions/381571/syndication-failing-with-error-iwksy1072e-could-no.html
Syndicating large libraries, some items failed to be syndicated, and the syndicator portlet shows the following message:
IWKSY1072E: Could not determine the root cause of this failure. An unexpected error has occurred while updating this item. Contact your Administrator.
SystemOut.log shows the following error at the same time the syndication fails:
=====================
00011ebd Report E com.ibm.workplace.wcm.services.repository.RepositoryException: Message: PrivilegedActionException caught, Cause: com.ibm.workplace.wcm.services.report.ReportStoreException: com.ibm.workplace.wcm.services.repository.RepositoryException: Message: Could not save object in repository., Cause: javax.jcr.RepositoryException: RT0002E: Error while calling a function updateItems of PLS data manager
com.ibm.workplace.wcm.services.report.ReportStoreException: com.ibm.workplace.wcm.services.repository.RepositoryException: Message: PrivilegedActionException caught, Cause: com.ibm.workplace.wcm.services.report.ReportStoreException: com.ibm.workplace.wcm.services.repository.RepositoryException: Message: Could not save object in repository., Cause: javax.jcr.RepositoryException: RT0002E: Error while calling a function updateItems of PLS data manager
at com.ibm.workplace.wcm.data.report.Report.save(Report.java:578)
..
.....
Caused by: com.ibm.icm.ci.data.CDMContentException: RT0002E: Error while calling a function updateItems of PLS data manager
at com.ibm.icm.ci.data.impl.ContentExceptionMap.getMappedException(ContentExceptionMap.java:76)
at com.ibm.icm.ci.data.impl.dautils.PUpdateNodeImpl.persistUpdatedContents(PUpdateNodeImpl.java:1007)
at com.ibm.icm.ci.data.impl.ContentService.update(ContentService.java:390)
at com.ibm.icm.ci.data.impl.ContentService.update(ContentService.java:337)
at com.ibm.icm.jcr.NodeImpl.save(NodeImpl.java:2656)
... 48 more
Caused by: com.ibm.icm.da.DBAccessException: com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-289, SQLSTATE=57011, SQLERRMC=ICMLFQ32, DRIVER=4.17.29
at com.ibm.icm.da.portable.data.WideTableData.changeItems(WideTableData.java:1863)
at com.ibm.icm.da.portable.data.WideTableData.updateItems(WideTableData.java:196)
at com.ibm.icm.da.portable.data.DataManager.updateWideItems(DataManager.java:1138)
at com.ibm.icm.ci.data.impl.dautils.PUpdateNodeImpl.persistUpdatedContents(PUpdateNodeImpl.java:1000)
... 51 more
Caused by: com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-289, SQLSTATE=57011, SQLERRMC=ICMLFQ32, DRIVER=4.17.29
at com.ibm.db2.jcc.am.hd.a(hd.java:752)
at com.ibm.db2.jcc.am.hd.a(hd.java:66)
at com.ibm.db2.jcc.am.hd.a(hd.java:135)
at com.ibm.db2.jcc.am.wo.b(wo.java:2422)
at com.ibm.db2.jcc.am.wo.c(wo.java:2405)
at com.ibm.db2.jcc.t4.ab.l(ab.java:408)
===============================portaldigexpwcmsyndicationdigexp portal wcm syndicationWed, 14 Jun 2017 20:06:19 GMTDVelBaezaSyndicating Local Schedules to IER via the Information Typeshttps://developer.ibm.com/answers/questions/374868/syndicating-local-schedules-to-ier-via-the-informa.html
When syndicating local schedules from Atlas to IBM Enterprise Records, why (or is it) necessary to associate every Information Type on the local schedule with the Policy Distribution Data Source? Only the retention period associated with the schedule appears to get syndicated, not each individual Information Type. Can we just add the Policy Distribution Data Source to a single Information Type? Thanks.ecmsupportatlasreleasesyndicationholddeactivateinactiveFri, 12 May 2017 19:17:28 GMTdrstarkMonitor syndication progresshttps://developer.ibm.com/answers/questions/366748/monitor-syndication-progress.html
how can I monitor the syndication task progress? how many contents syndicated during the current active syndication, the total number of contents to be syndicated?portaldigexpwcmportal 8.5syndicationwcm_8.5Wed, 05 Apr 2017 13:11:39 GMTKhaled_GhareebIs it possible have multiple intervals for a syndication pair?https://developer.ibm.com/answers/questions/365466/is-it-possible-have-multiple-intervals-for-a-syndi.html
Is it possible have multiple intervals for a syndication pair?syndicationintervalTue, 28 Mar 2017 14:24:04 GMTMishaSShaikhAnnonymous users cannot access the content after 1st syndication attempt.https://developer.ibm.com/answers/questions/362282/annonymous-users-cannot-access-the-content-after-1-1.html
Annonymous users cannot access the content after 1st syndication attempt.accesssyndicationcontentTue, 14 Mar 2017 15:31:53 GMTMishaSShaikhAnnonymous users cannot access the content after 1st syndication attempt.https://developer.ibm.com/answers/questions/362281/annonymous-users-cannot-access-the-content-after-1.html
Annonymous users cannot access the content after 1st syndication attempt.accesssyndicationcontentTue, 14 Mar 2017 15:31:00 GMTMishaSShaikhAutomatic syndication stuck in "Pending" statushttps://developer.ibm.com/answers/questions/355205/automatic-syndication-stuck-in-pending-status.html
Hi,
I am using WebSphere Portal 8.0.0.1 CF 20.
Enabled the automatic syndication with following configuration. But whenever content published, the syndication status changed to "Pending" and none failed items and stuck there. There is no error on trace.log and SystemOut.log
When I click the **update syndicator** icon then it is syndicating to target server.
**WCMConfigServices**
connect.moduleconfig.syndication.inittasks=true
deployment.itemChangedTaskDelay=60
deployment.subscriberOnly=false
Also I changed the below for trouble shooting the issue. But no luck.
The syndication tracestring is: com.aptrix.deployment.*=all:com.aptrix.syndication.*=all
Increased total transaction lifetime timeout to 480 seconds: WAS Admin Console > Servers > WebSphere application servers > WebSphere_Portal > Container Services > Transaction Service.
Any idea to fix this issue?
ThanksportaldigexpwcmsyndicationThu, 09 Feb 2017 05:31:29 GMTVSethuManual syndication is automatically triggered with subscriber restarthttps://developer.ibm.com/answers/questions/350817/manual-syndication-is-automatically-triggered-with.html
Manual syndication is automatically started when subscriber is restarted.
I need to avoid this behavior and only syndicate new content when I press the "update" button.portaldigexpwcmsyndicationWed, 25 Jan 2017 13:33:29 GMTDVelBaezaCross Version Syndication to Portal version 9.0https://developer.ibm.com/answers/questions/348875/cross-version-syndication-to-portal-version-90.html
Is Cross version syndication supported from v7 (Syndicator) to v9 (Subscriber) ?portaldigexpwcmsyndicationTue, 24 Jan 2017 13:45:14 GMTMRPooleWhy do we have to manually update our Forms Experience Builder URL every time we Syndicate?https://developer.ibm.com/answers/questions/327985/why-do-we-have-to-manually-update-our-forms-experi.html
When we authenticate Forms applications (FEB) URL changes on our application page and we have to manually update manually every time after Syndication. We have the application URL configured on the portal console as a custom property.
Every time after Syndication, the Application URL for all Forms on the subscriber portal page gets updated to the Syndicator Forms URL thus we have to to update the URL to the subscriber Forms URL.portalsyndicationweb content managerTue, 13 Dec 2016 19:28:59 GMTTony DonatoException java.util.ConcurrentModificationException seen during syndication of WCM libraries.https://developer.ibm.com/answers/questions/324293/exception-javautilconcurrentmodificationexception.html
Exception java.util.ConcurrentModificationException seen during syndication of WCM libraries.portaldigexpwcmsyndicationWed, 30 Nov 2016 19:06:46 GMTrickett