Server comes with a command called RoomsAdminTool located at /Applications/Server.app/Contents/ServerRoot/usr/bin/RoomsAdminTool. This tool can list available rooms using a -l flag:

RoomsAdminTool -l

You can also create new rooms, using the following format, where krypted is the name of the room, the persistent option means the room is, er, persistent. The description option indicates a description used for the room.

RoomsAdminTool -n krypted -c persistent yes description "This room is for friends of krypted only”

To then delete the room, use the -d option:

RoomsAdminTool -n krypted -d

Add the -v to do it all verbosely. There are lots of other options as well, as follows (from the man page): Valid Configuration Keys and Values:

KEY	VALID VALUES	DESCRIPTION
description	string	A short description for the room
password	string	Define a password for room entry. An empty string implies no password required.
membersOnly	yes | no	Only room members are allowed to enter the room.
subjectLocked	yes | no	Are non-moderators and non-admins prevented from setting the room subject
logFormat	Disabled | Text | XHTML	Disable room logging, or enable it using Text or XHTML.
maxUsers	integer; 0 for unlimited	Set the maximum allowed occupants for the room.
moderated	yes | no	Make the room "moderated".
nonAnonymous	yes | no	If "yes", only moderators/owners can discover occupants' real JIDs.
persistent	yes | no	Persistent rooms stay open until they are explicitly destroyed and their configuration survives service restarts, unlike non-persistent rooms.
privateMessagesAllowed	yes | no	Whether or not occupants can exchange private messages within the room.
roomPublic	yes | no	Defines whether the room be discovered by anyone
subject	string	Set a room subject/topic
usersCanInvite	yes | no	Defines whether occupants can invite other users to enter the room
addOwner	valid JabberID	Make the specified user a room owner (ex.: [email protected]). Rooms can have multiple owners.
removeOwner	valid JabberID	Remove the specified user from the room owner list
addAdmin	valid JabberID	Make the specified user a room admin
removeAdmin	valid JabberID	Remove the specified user from the room admin list
addMember	valid JabberID	Make the specified user a room member
removeMember	valid JabberID	Remove the specified user from the room member list
addOutcast	valid JabberID	Make the specified user a room outcast (banned from public rooms)
removeOutcast	valid JabberID	Remove the specified user from the room outcast list

Ultimately, if you’d like to do Student Information System (SIS) integration, or wait for an AD/OD group and then programmatically generate rooms, this is how you’d do it. Also, it’s worth noting that Messages (and so Jabber if you’re running your own server) is a very basic instant messaging tool. There are more modern ways of interacting with others these days, including Slack and Confluence. Additionally, the Messages app can just use the phone number of people to let address books become a way of managing groups you’d like to message. These do not require a dedicated server, but most strategies will require a monthly fee that’s typically per-user.

The post Programatically Manage Jabber Chat Rooms In macOS Server appeared first on krypted.com.