I have a custom HTML page that is deployed to each cognos stack. The
standard way to reference this page would be to use relative URLs but
the cognos viewer doesnt allow them. My current line of thinking is to
archive the portal page with a known tag as the url and then write some
code to automatically unpack the archive and replace the tag with the
appropriate url based on properties passed into our own install
program. The problem with this is that the export of the portlet is
very cryptic. I've pasted a snippet of an html viewer portlet extract
that points to http://www.google.com. I'm hoping someone can help me
enterpret this extract so I can manipulate the url inside of it.
By
the way, I know this is "working as designed" based on the doc but I
really need a workaround to this issue.
<object>
<class>portletInstance</class>
<name>31400BA4E369B352E40750849FFFBD2E</name>
<parentId>3</parentId>
<storeID>iB343497EE14640F6B9BA9E6763F2DBE4</storeID>
<props>
<creationTime>
<value>2010-12-03T18:38:25.358Z</value>
</creationTime>
<modificationTime>
<value>2010-12-03T18:52:51.482Z</value>
</modificationTime>
<name>
<value><item><locale xsi:type="xsd:string">en-us</locale><value xsi:type="xsd:string">31400BA4E369B352E40750849FFFBD2E</value></item>
</value>
</name>
<owner>
<value><item><searchPath xsi:type="cm:stringProp">
<value xsi:type="xsd:string" xml:space="preserve">CAMID("secldap:a:CN=cognosadmin,OU=Cognos Roles,OU=Reno,DC=archmod,DC=local")</value>
</searchPath>
<storeID xsi:type="cm:guidProp">
<value xsi:type="cm:guid" xml:space="preserve">xc2VjbGRhcDphOkNOPWNvZ25vc2FkbWluLE9VPUNvZ25vcyBSb2xlcyxPVT1SZW5vLERDPWFyY2htb2QsREM9bG9jYWw_</value>
</storeID></item>
</value>
</owner>
<context>
<value><wsrp:portletContext xmlns:wsrp="urn:oasis:names:tc:wsrp:v1:types"><wsrp:portletHandle>html:EBBAEC0860CFCDFD8090DA38C1F7D878</wsrp:portletHandle><wsrp:portletState>H4sIAAAAAAAAAIVWQW7DMAz7ytC72mHALkPX654xOI4Tu0kcw3baLa+fUmDYYQh5DiPREkXpnEw201M0k3s/1FBH9+lG6fPhcj49Pl3O/xFlkDJAhCvi4w7CehOjG9n/6RsihlkGzHIqLMWyl2LJSs/Xmsrb6XS/34/9PPejO9p5AhHzjBNGWZTSxyMU5C3NXu3+qmMYoqFs1jtEhCIBl/BKSbSYRJdlXBhNi7NErKSKReKzeIzYiu0YwpAYUeJKSinXBBGZFKqIxSS02A19SLlBRBol0cmdvujgYV0pU+tJ04X0vQvSBYhonZhKeVCJO8tab3DnUpWG+O1NCu7c6sVjRw4t+SwEQapJDD3gSvtFPK4SWTi7Q+zrNH4uRY1gwx0unRkLct9tjrBpqW6IOjVGj9/rsMFHzCAvsmBdKkdurCuO0WFRWjzDyqDFmq2kiJFJ2pEFH6XBG27AZQ6VNVpHN+FGrzhAa6TFj6xZyAojSzrOwuVElktLXdDi8debZsL3HKmjNjNgOWm3iMmoSVYsCDV8onqyH7djAQfQzUW2MDFCfcVE+jkLOUXJZG5bDYtKSVh6o95IliilZ1kIompLqRdHsrki64hVfePzTWMkamd9Q24rdgSwFawzsteUxxr0LvReZ+Tl9fkX9APfKX4eAA4AAA==</wsrp:portletState></wsrp:portletContext></value>
</context>
<portlet>
<value><item><searchPath xsi:type="cm:stringProp">
<value xsi:type="xsd:string" xml:space="preserve">/portal/portalPackage[@name='Connection']/portletFolder[@name='Portlets']/portletProducer[@name='Cognos Utility']/portlet[@name='HTML Viewer']</value>
</searchPath>
<storeID xsi:type="cm:guidProp">
<value xsi:type="cm:guid" xml:space="preserve">iC7DB682615304436934D58A9EBF3FC89</value>
</storeID></item>
</value>
</portlet>
</props>
</object>
Ok, I figured this out. What you can do is create an html source portlet and use an object tag to imbed the page:
<OBJECT DATA='hello.html' HEIGHT='200' WIDTH='200'></OBJECT>