• State Not Answered
  • Replies replies
    8
  • Subscribers subscribers
    15
  • Views views
    1007
  • Users 0 members are here
  • Locked Locked
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

GroupWise REST API

dschaldenovell
 
Good morning,
 
Customer is attempting to use REST to move a GW Resource, the Resource has a "/" symbol in it, for example: my/resource~ when they attempt to perform the move there is an error, which we are assuming is the issue with the "/" is there a way to encapsulate that Resource name such as in single quotes 'my/resource' or double quotes "my/resource"
 
Thank you for any assistance that can be offered
 
Daniel

Tags:

Parents Reply
  • 0   in reply to   

    Good morning 

     

    This is from the customer 

     

    Not sure I am following what this is. Is this a command that should allow us to move the resource without worrying about the association?

     

    Basically when we tried to move the object previously, it was encountering an error with a Sync Error. So to the question above would this take into account any Associations? 

     

    Thank you, 

     

    Daniel  

Children
  • 0 in reply to   

    Hi,

    A resource should not have any association. It does not have an LDAP counterpart.

    Cheers,

     

  • 0   in reply to 

    Good morning, 

     

    That is part of the issue, the Resource in Question was created in an earlier version of GroupWise (prior to GW 2012) back-line provided us/customer with a script that was supposed to sever that association so that the Resource could then be moved.

    The customer is/was attempting to run the script on that Resource, and that's when they are receiving the error, which again seems to be because the Resource has a "/" in it's name. Another Engineer suggested doing the following: "Cxx/Rexxxls" or "Cxx\/Rexxxls" so the command would look something like this, https://10.xx.xx.xx:9710/gwadmin-service/domains/BxxMxxO/postoffices/PO1/users/Cxx/Rexxxls~/directorylink

     

    The customer is going to be trying again today

     

    Thank you, 

    Daniel 

  • 0 in reply to   

    Hi Daniel,

    If that doesn't work you could consider renaming the resource first to remove the illegal characters:

     

    curl -k --user admin:password -H "Content-Type:application/json" -X POST ipofserver:9710/.../rename --data '{"objectId":"RESOURCE.dom1.po1.Test Resource","newObjectId":"TestResource"}'

     

    In the example above the resource had a space in the name.  This should work with any other illegal character.

     

    Cheers,

     

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.