• State Suggested Answer
  • Replies replies
    12
  • Answers answer
    1
  • Subscribers subscribers
    18
  • Views views
    470
  • Users 0 members are here

Tool for editing domain databases

Prindl

Recently I checked the database entries for my MTAs, Internet Agents and POAs, because i saw a path in a log, which does not exist since years.

In this case it was the UNC-path (attribute-ID 59003), which is totally wrong for this agent, because it points to a server, which was removed several years ago. I know, that one could set this attribute via C1 as long as the groupwise system was integrated into eDir, but now, I don't see any tool to change this value. Although that value seems to be not used any more I see this value still popuated in a newly installed internet agent, but it does not show an UNC-path - it simply shows the linux filesystem-path to the internet agent.

How can I get rid of those irritating entries, because if someone has to take over the administration of this system, this will at least lead to unneccessary thoughts. And I hate carrying along wrong entries - even, if they do not harm and apparently are not used.

Parents
  • 0  

    What is the record showing when using the REST API?

    https://gwserver:9710/gwadmin-service/domains/DOM_NAME/mta

    As i dont have this i like to see the full record as this probably can be used to make a REST API call using Curl to empty or remove this field

  • 0 in reply to   

    You think, that if I do a GET of https://gwiaserver.x.x:9710/gwadmin-service/domains/DOM-NAME/gwias/GWIA-NAME

    and afterwards change in the body the "path" entry and then do a PUT of the changed body to the same uri as above, the entry is changed accordingly?

    I have no experience with the groupwise RestAPI and how reliable it is. I only use RestAPIs for Databases, where I have the full control over the database itself and use the RestAPI to provide limited access to other users.

    For being on the safe side, which files should i backup before changing anything, so that I can go back to a working configuration, if anything goes wrong? Is it just the wpdomain.db or does it include gwdom.dc and wpdomain.dc and wphost.dc. And is it sufficient to backup this(those) files on the domain server, where the gwia runs, or do I have to backup the primary domain database, too.

    Regards

Reply
  • 0 in reply to   

    You think, that if I do a GET of https://gwiaserver.x.x:9710/gwadmin-service/domains/DOM-NAME/gwias/GWIA-NAME

    and afterwards change in the body the "path" entry and then do a PUT of the changed body to the same uri as above, the entry is changed accordingly?

    I have no experience with the groupwise RestAPI and how reliable it is. I only use RestAPIs for Databases, where I have the full control over the database itself and use the RestAPI to provide limited access to other users.

    For being on the safe side, which files should i backup before changing anything, so that I can go back to a working configuration, if anything goes wrong? Is it just the wpdomain.db or does it include gwdom.dc and wpdomain.dc and wphost.dc. And is it sufficient to backup this(those) files on the domain server, where the gwia runs, or do I have to backup the primary domain database, too.

    Regards

Children

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.