| 00:00 | Start of recording; Presentation |
| Phone Questions: |
| 0:56:34 | Q: People often place authoring and delivery in one system. Is this a good practice?
A: Having both authoring and delivery WCM functions on the same system is a good practice depending on the usage scenario.... |
| 0:59:09 | Q: (On slide 12), You showed a cluster without Portal; only WCM. Is that possible?
A: No, WebSphere Portal Server was implied. |
| 1:01:45 | Q: Our Portal servers are supporting multiple realms. We are using a single LDAP source and the Ltpa token is produced from another system. Will this be an issue with WCM security?
A: This scenario does present any immediately obvious issues. Testing will be required for validation. |
| 1:03:11 | Q: Can each library have its own syndication with its own settings?
A: Yes |
| 1:06:11 | Q: Is there a way to hide the name field in the authoring template so that a user just uses title and description?
A: No. |
| 1:08:10 | Q: If we use in-line editing, does that mean we have to implement delivery and authoring WCM instances on the same physical node?
A: Locating both instances on the same node is not a requirement, but a best practice. |
| 1:09:37 | Q: We're using a multilingual template and Portal 5. Does Portal 6 allow us to continue with this?
A: There is new improved multilingual functionality in release 6.0.1.2. |
| 1:13:50 | End of Recording |
| Webcast questions: |
| 1 | Q: Can we have a library of design components, such as the authoring templates, sites, etc, and then move that library between environments during code migrations?
A: Answer is yes. In fact this is a "best practice" for WCM. See the WCM Best Practices document for more information. |
| 2 | Q: What are the benefits of using library partitioning? Is library partitioning available for the purpose of reducing the amount of data that needs to be syndicated?
A: That is not the main purpose of a library, but could certainly have that effect. And just for clarity, you do not partition a library--you have multiple libraries. Explanation of libraries and library use is really beyond the scope of this particular presentation, but more information may be found in the WCM Infocenter, and the WCM Best Practices wiki and document (cited in question 1, above). |
| 3 | Q: In the future, can we configure syndication to run only at particular times of the day?
A: Yes, in the future plans, but this functionality is not planned for Version 6.1. |
| 4 | Q: Is WCM content stored in JCRDB and no longer in the WCMDB?
A: Yes, since Version 6.0, Web Content Management data is stored in the JCR. |
| 5 | Q: What does "version" mean in reference to: Sending (all items), for example: "Version to Gatherer"?
A: By default, each piece of content is automatically versioned in the JCR when an existing piece of content is edited. Syndication will syndicate the versions as well as the latest item. |
| 6 | Q: Should the WCM subscriber and WCM syndicator be at the same versioned item level (such that all versions of an item will be syndicated)?
A: They will be at the same level when syndication completes successfully. Not to be confused with Portal and WCM Version levels (the version levels of the SOFTWARE must be the same for syndication to work). |
| 7 | Q: Do we need to stop/start the WCM server after modifying syndication to run manually?
A: If you modify the properties file, yes, you need to stop/start for that modification to take effect, however you can do a manual syndication at any time from the Syndicator Admin screen. |
| 8 | Q: Is there some way to "batch" the setup of syndicator/subscriber relationships similar to the Portal's xmlaccess tool?
A: No, there is no tool similar to xmlaccess for building WCM syndicator/subscriber relationships. |
| 9 | Q: Does the syndicator and subscriber need to be on the same iFix level for syndication to be successful, correct?
A: Yes |
| 10 | Q: Is there a history of syndication status stored anywhere?
A: There is no history maintained for syndication, the information for the last syndication can be viewed in either the syndicator/subscriber form. |
| 11 | Q: Can we get email sent out to the WCM administrator when the syndication operation fails? (slide 24)
A: No, this functionality is not currently available. If you monitor the log file with ITCAM or other monitoring tool, this type of notification can be coded based upon messages logged. |
| 12 | Q: Do we need to delete a library from a WCM Subscriber which was received from the Syndicator, but has since been renamed on the Subscriber machine?
Do you see any issues with doing this renaming of a WCM library on the subscriber?
A: Syndication is based on Library ID not the name of the library. However, WCM support does not recommend renaming a WCM library, as that name stored in other parts of the WCM product, and renaming a library may cause lookups to fail in certain scenarios. |
| 13 | Q: On which screen do you specify whether to syndicate all items or only published items?
A: Syndicator screen; when you add a library for syndication, you click a radio button for All or Live. |
| 14 | Q: Is EventLog is available in older versions of WCM?
A: No, the web content event log is not available in versions prior to v6. |
| 15 | Q: What are the table names which stores WCM data in JCR database
A: Data is stored in many tables across the JCR database Please contact support for help with identifying the names of these tables. |
| 16 | Q: When WCM is clustered, which node contains the event Database? Which node do you run the clear event log task?
A: The Event Log database is "contained" on all nodes, as in other databases in a typical cluster. The task can be run on any node in the cluster. |
| 17 | Q: Can the syndication be run using scripts?
A: There is no API for running WCM syndication. |
| 18 | Q: Do changes to the JCR on a subscriber show up in the JCR audit log?
A: Yes, if the audit log is enabled on the subscriber system. The JCR itself has no knowledge of a syndicator or subscriber system, it only sees updated content to the repository, so it will behave similarly on both systems in this respect. |
| 19 | Q: What is the URL for the WCM Best Practices wiki?
A: WCM Best Practices wiki https://info2.lotus.com/lotus/quickr |
| 20 | Q: I have heard that it is highly recommended to upgrade to 6.0.1.2, and now to 6.0.1.3 version in order to have syndication function correctly. Is this true?
A: There were a number of fixes to WCM in this latest release, which is 6.0.1.3. |
| 21 | Q: How can I ensure that items are not locked on a WCM subscriber?
A: You can check for locked items using the Portal Administration |
| 22 | Q: If you are not supposed to do in-line editing on a delivery server, then why does the option exist to do two-way syndication? This scenario seems like the perfect opportunity to use this functionality.
A: Two-way syndication is intended to be used between two authoring environments. |
| 23 | Q: During the presentation, you mentioned moving JSP's separately. Does this mean that we need to create the JSP on subscriber again, or is there a manual way of moving JSPs from the syndicator WCM server to a subscriber?
A: JSP files are text files and can be moved just as you would move any other file from one system to another.
|
| 24 | Q: Can WCM tracing be turned on and off dynamically? (Without having to restart the server)
A: Yes, WCM tracing (including syndication) can be enabled via the WAS Admin Console, which requires a restart but starts set across restarts, or dynamically via the Portal Admin Trace portlet. Either method functions fine. |
| 25 | Q: Are there any plans in the future for a PDM syndication function?
A: There are no plans for syndication of PDM documents. The recommended approach to get files syndicated is to store the documents inside of WCM as content items using a authoring template that has a file resource component. Once the documents are stored natively inside of WWCM, users can link, display, and syndicate the documents. |
| 26 | Q: Are there any plans in the future for a PDM syndication function?
A: There are no plans for syndication of PDM documents. PDM functionality is being replaced with a function similar to what is found in Lotus Quickr in a future release. The recommended approach to syndicate files to another machine is to store them as file components in WCM inside a content item using a authoring template. |
| 27 | Q: Is there any way to disable the in-line editing?
A: If you are looking to enable on in the authoring environment, you can set different right on the library in delivery such that nobody will have rights to edit. This action will effectively disable in-line edits in delivery. |
| 28 | Q: On the syndicator-subscriber pairs, why can we not just point the subscriber to the syndicator without having to copy the ids (manually) from one machine to another?
A: The reason for this behavior is that WCM needs to create a one-to-one mapping of the subscriber/syndicator pair. Since its possible to have more than one subscriber defined on a system, without supplying the ID, the WCM subscribers would not know with which subscriber to communicate. |
| 29 | Q: I publish a library to a WCM subscriber, then I delete the library on the subscriber. What happens the next time syndication runs? Does the library get propagated to the WCM subscriber again?
A: If you delete a library, it is recommended that you recreate the syndicator/subscriber pairs. This guarantees that the subscriber receives all the necessary data. If the syndicator/subscriber pair is not recreated, bare in mind that the next syndication may fail, and if this occurs, the syndication mechanism may only send updates since the last syndication, resulting in missing references and other issues. |
