Confluence Converter

instructions

To use acconverter you need to specify parameters in xml file, named "mindtouch.deki.acconverter.exe.xml". This flie must located in acconverter directory. Example of this file is in mindtouch.deki.acconverter project directory.
ConfluenceAPIUrl - path to Confluence API, for example http://localhost:8082/rpc/soap-axis/confluenceservice-v1.
ConfluenceUserName and ConfluenceUserPassword - login and password of confluence user. Acconverter uses it for connecting to Confluence to recive data.
DreamAPIUrl - path to dream api, for example http://localhost:8081/deki/.
DekiUserName and DekiUserPassword - Deki admin user name and password. Used to store data to Deki.
CompatibleConvertUserPermissions - true convert permissions as they can be setted through Deki interface. If false acconverter will try to set different roles to users on pages, according to their permissions in Confluence. You wrote to me about this parameter at 13/10/2008.
SpacesToImport - list of spaces to import. If no space specified - all spaces will be imported.
We can select spaces using
<SpacesToImport>
 <Space>SpaceTitle</Space>
</SpacesToImport>

Goal: Use Confluence's SOAP API to import data into Deki. 

Phase 1 goals

• Spaces:
  • In the long-term, the tool should be able to accept a list of spaces to import - for the first pass, we import all spaces at once.
• Users:
  
  • Convert all users into Deki users
    • If password hashing mechanism is different, reset to random string (people can use "Forgot password" feature to their email addresses)
  • Admin account
    • How does the MW convert handle users? (I'm assuming the pwd hashing isn't a problem)
    • How to handle user account conflicts? (What if "Admin" exists in Deki, and then an "Admin" user comes in from Confluence?)
• Pages:
  • Put all pages in XHTML format into Deki
  • Do not worry about revisions; just get the latest copy
• Attachments:
  • Attach files onto pages
  • (How are internal links to attachments handled inside Confluence?)
• Labels:
  • Convert labels to tags and maintain all page associations (spaces get converted into a root-level hierarchy page, so they can also be tagged)
• Comments:
  • Maintain all comments
• Permissions:
  • Maintain all permissions per-page
• Macros:
  • Do not worry about macros - does renderContent execute macros?