Skip to main content
This forum is closed to new posts and responses. New discussions are now taking place in the IBM Developer Answers forum.
 
developerWorks
AIX and UNIX
Information Mgmt
Lotus
New to Lotus
Products
How to buy
Downloads
Live demos
Technical library
Training
Support
Forums & community
Events
Rational
Tivoli
WebSphere
Java™ technology
Linux
Open source
SOA and Web services
Web development
XML
My developerWorks
About dW
Submit content
Feedback



developerWorks  >  Lotus  >  Forums & community  >  IBM Sametime Forum

IBM Sametime Forum

developerWorks

  

PreviousPrevious NextNext


Brian Thornock 1.Apr.11 07:00 PM a Web browser
Administration 8.5.1 Linux; Windows


Hi,

I'm trying to configure our managed-settings.xml on our ST server to automatically enable Telephony and Presence settings for all the clients.

I'm following the instructions at
Lotus Sametime 8.5.1 Installation and Administration -> Installing -> Deploying the Sametime client to users -> Enabling Sametime Unified Telephony, extended status, and telephony status in the client.

At the bottom of the article, it describes how to set up this file and even gives an example of what the managed-settings.xml should look like. I copy-and-paste this text verbatim into a file on my server. Owned by root user, but chmod'ed permissions to 777.

Over on my Media Manager in the Console, Sametime System Console|Manage Policies|Instant Messaging|Sametime Instant Messaging Default Policy|Plugin Management, I check "Allow user to install plugins" and enter the URL of the directory where my managed-settings.xml resides:
http://sametime1.avaya.com/ST851GA/update-site-851/

I click OK and restart Domino and Sametime to pick up the changes.

Over in my 8.5.1 Connect Client, I log in and select Tools|Plug-ins|Install Plug-ins|Search for new features|Add Remote Location|, type in the URL of the remote directory to my managed-settings.xml file and pick an arbitrary name. Click OK and Finish.

Uh-oh. I see "CWPPR0031W: The requested provisioning operation(s) completed with partial success.
Network connection problems encountered during search.
Unable to access "http://sametime1.avaya.com/ST851GA/update-site-851/".
Error parsing site stream. [White spaces are required between publicId and systemId.]
Error parsing site stream. [White spaces are required between publicId and systemId.]

No acceptable features were found on the selected site(s). Choose a different site or site category."


Hmm. Run google searches and search the developer forums but don't find any solution.

I see
Lotus Sametime 8.5.1 Installation and Administration -> Configuring -> Configuring the Sametime client -> Setting client preferences -> Configuring Sametime Connect client preferences with the Expeditor managed settings framework

and it says I can include in my client the setting:
com.ibm.collaboration.realtime.policy.sametime.managedsettings.level=FINEST
for more information.

I do that and now not happy to see a SAXParseException in the log. Hmm. Maybe the xml file is invalid, so I run unix2dos, and then dos2unix on managed-settings.xml in case of line-ending issues with no change. Then I browse to that URL from the client machine and am able to view the contents of the file as I thought:
<ManagedSettings>
<settingGroup name="com.ibm.collaboration.realtime">
<setting name="enableSUT" value="false"/>
<setting name="enableTelephonyStatus" value="true"/>
<setting name="enableExtendedStatus" value="true"/>
</settingGroup>
</ManagedSettings>


OK, then I add an xml tag to the top of managed-settings.xml to try that in case not happy about the xml:
<?xml version="1.0" encoding="UTF-8"?>
and that doesn't work.

Then I create a site.xml file at the same location with these same attributes and values wrapped by the XML header and <site> ... </site> but that doesn't work.


Then, I get creative and try manually editing the Connect Client's plugin_customization.ini file and set the 2 values to true for telephony and presence. I restart the client and my telephony and presence work! Excellent! But, I want to push these settings out to all clients without requiring them to do this, just like the ST docs instruct. Hmm.

I put this file on another server in another domain in case of odd network issues with the same result. I then add the IP address of this machine hosting the managed-settings.xml file to the list of Trusted Servers in Sys Console in case it wasn't trusted; restart Domino & Sametime. No change.

Am I missing some configuration here, either on the Connect Client or the Sametime server? Perhaps Apache HTTPD which is serving the file? I can browse to the file and view its contents from IE and Firefox from the client machine. But Connect always fails with this same SAX Parsing error.

Anyone else have any luck using the managed-settings.xml file? And if so, how did you configure it? Manually editing the config file works as a good workaround for now.


<CommonBaseEvent creationTime="2011-04-01T15:44:08.308-06:00" globalInstanceId="ELa9fede3700012f1305532a0000000c" msg="CWPPR0540W: An unexpected error occurred while searching for feature on update site http://sametime1.avaya.com/ST851GA/update-site-851/." severity="30" version="1.0.1">
<extendedDataElements name="CommonBaseEventLogRecord:level" type="noValue">
<children name="CommonBaseEventLogRecord:name" type="string">
<values>WARNING</values>
</children>
</extendedDataElements>
<extendedDataElements name="CommonBaseEventLogRecord:sourceClassName" type="string">
<values>com.ibm.rcp.provisioning.internal.requirements.UpdateChecker</values>
</extendedDataElements>
<extendedDataElements name="CommonBaseEventLogRecord:sourceMethodName" type="string">
<values>handleSearchException</values>
</extendedDataElements>
<extendedDataElements name="CommonBaseEventLogRecord:Exception" type="string">
<values>org.eclipse.core.runtime.CoreException: Network connection problems encountered during search.
at org.eclipse.update.search.UpdateSearchRequest.performSearch(Unknown Source)
at com.ibm.rcp.provisioning.internal.requirements.UpdateChecker.performEnhancedSearch(Unknown Source)
at com.ibm.rcp.provisioning.internal.impl.ProvisioningServiceImpl.search(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.update.ui.UpdateJob.runSearchForNew(Unknown Source)
at org.eclipse.update.ui.UpdateJob.run(Unknown Source)
at org.eclipse.core.internal.jobs.Worker.run(Unknown Source)
Contains: Unable to access &quot;http://sametime1.avaya.com/ST851GA/update-site-851/up</values>
<values>date-site-851/&quot;.
Contains: Error parsing site stream. [White spaces are required between publicId and systemId.]
</values>

msg="Network connection problems encountered during search."

<extendedDataElements name="CommonBaseEventLogRecord:Exception" type="string">
<values>org.eclipse.core.runtime.CoreException: Error parsing site stream. [White spaces are required between publicId and systemId.]
at org.eclipse.update.core.Utilities.newCoreException(Unknown Source)
at org.eclipse.update.core.Utilities.newCoreException(Unknown Source)
at org.eclipse.update.core.model.SiteModelFactory.parseSite(Unknown Source)
at org.eclipse.update.internal.core.SiteURLFactory.createSite(Unknown Source)
at org.eclipse.update.internal.core.InternalSiteManager.createSite(Unknown Source)
at org.eclipse.update.internal.core.InternalSiteManager.createSite(Unknown Source)
at org.eclipse.update.internal.core.InternalSiteManager.createSite(Unknown Source)
at org.eclipse.update.internal.core.InternalSiteManager.attemptCreateSite(Unknown Source)
at org.eclipse.update.internal.core.InternalSiteManager.getSite(Unknown Source)
at org.eclipse.update.core.SiteManager.getSit</values>
<values>e(Unknown Source)
at org.eclipse.update.search.UpdateSearchRequest.searchOneSite(Unknown Source)
at org.eclipse.update.search.UpdateSearchRequest.performSearch(Unknown Source)
at com.ibm.rcp.provisioning.internal.requirements.UpdateChecker.performEnhancedSearch(Unknown Source)
at com.ibm.rcp.provisioning.internal.impl.ProvisioningServiceImpl.search(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.update.ui.UpdateJob.runSearchForNew(Unknown Source)
at org.eclipse.update.ui.UpdateJob.run(Unknown Source)
at org.eclipse.core.internal.jobs.Worker.run(Unknown Source)
Caused by: org.xml.sax.SAXParseException: White spaces are required </values>
<values>between publicId and systemId.
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)
at org.apache.xerces.impl.XMLScanner.scanExternalID(Unknown Source)
at org.apache.xerces.impl.XMLDocumentScannerImpl.scanDoctypeDecl(Unknown Source)
at org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)</values>
<values>
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at org.eclipse.update.core.model.DefaultSiteParser.parse(Unknown Source)
... 19 more
</values>
</extendedDataElements>
<sourceComponentId component="Expeditor 6.2" componentIdType="ProductName" instanceId="1300746781187" location="aud007606" locationType="Hostname" subComponent="org.eclipse.update.core" threadId="8" componentType="http://www.w3.org/2001/XMLSchema-instance"/>

Thanks,
Brian






managed-settings.xml Error parsing ... (Brian Thornock 1.Apr.11)
. . RE: managed-settings.xml Error pars... (Maik Weber 7.Jun.11)





  Document options
Print this pagePrint this page

 Search this forum

  Forum views and search
Date (threaded)
Date (flat)
With excerpt
Author
Category
Platform
Release
Advanced search

 RSS feedsRSS
All forum posts RSS
All main topics RSS
More Lotus RSS feeds

Resources

 Resources
Forum use and etiquette
Native Notes Access
Web site Feedback

Lotus Support

 Lotus Support
IBM Support Portal - Lotus software
Lotus Support documents
Lotus support by product
Lotus support downloads
Lotus support RSS feeds

Wikis

 Wikis
IBM Composite Applications
IBM Mashup Center
IBM Connections
IBM Connections Cloud Developers
IBM Docs
IBM Forms
IBM Mobile Connect
IBM Sametime
IBM SmartCloud for Social Business
IBM Web Experience Factory
Lotus Domino
Lotus Domino Designer
Lotus Expeditor
Lotus Foundations
Lotus iNotes
Lotus Instructor Community Courseware
Lotus Notes
Lotus Notes & Domino Application Development
Lotus Notes Traveler
Lotus Protector
Lotus Quickr
Lotus Symphony
IBM Web Content Manager
WebSphere Portal

Lotus Forums


 Lotus Forums
Notes/Domino 9.0
Notes/Domino 8.5 + Traveler
Notes/Domino XPages development forum
Notes/Domino 8
Notes/Domino 6 and 7
IBM Connections
IBM Mobile Connect
IBM Sametime
IBM SmartCloud Notes
Lotus Enterprise Integration
Lotus Protector
Lotus Quickr
Lotus SmartSuite