Packaging Requests

RealmJoin offers a Packaging-as-a-Services (PACKaaS) if application packages are required, that are not already available in the RJ store, or are outdated. This section shall give a comprehensive overview over different scenarios. For more detailed information get in touch with your RealmJoin consultant/partner/support.

Architecture (Win11 & macOS)

The glueckkanja Packaging Factory is currently optimized for Windows 11 application requests, providing comprehensive support and reliable packaging services for the Windows ecosystem. We are actively developing full macOS integration, which will significantly expand our capabilities and introduce hundreds of ready-to-use applications in the RealmJoin store, creating a more comprehensive cross-platform experience for our users.

While macOS packages remain in preview status as we continue to refine our macOS packaging pipeline, we accept macOS application requests on a best-effort basis. Our team will work diligently to accommodate these requests within our current development framework, though please note that processing times and availability may vary as we continue to enhance our macOS integration capabilities.

We appreciate your patience as we work toward delivering the same level of excellence for macOS that our Windows 11 users currently enjoy.

Request Types

Three different PACKaaS requests are currently available: new package, update existing package and organic packages.

Custom vs. generic packaging

Generic Packages in RealmJoin

We aim to create packages as generic as possible. This allows all settings to be configured via the RealmJoin portal post-app subscription. Our generic packages feature unmodified installers provided by vendors, without any customer-specific alterations. These packages are accessible to all customers in the RealmJoin store.

Custom Packages in RealmJoin

Custom packages are exclusively available for customers in their custom section of the RealmJoin store. The custom namespaces are used for modified installers, including those customized by the vendor for the customer, such as SAP, or for customer-developed apps and similar cases.

We invite customers to share their evaluation on whether an application can be packaged as generic or requires a custom package. However, the final decision is made by the glueckkanja Packaging Factory. Note that custom packages incur additional costs.

New Packages

If the application required is not already available in the RealmJoin store, it can be requested to be packaged via the RealmJoin packaging factory. A valid PACKaaS request must contain at least the following:

  • The binaries. A download URL is not sufficient, but might be provided for reference.

  • A documentation. All required configuration switches must be provided as command line parameters or registry keys or config files or similar. Screenshots are not sufficient. PACKaaS does not include Scripting-as-a-Service.

If the application package does not contain any customer specific information, it will be added as generic package to the public RealmJoin store, and if possible as a maintained package. All other application packages will be created as custom/private packaging. For fees please refer to the subscribed RealmJoin license options.

Package Updates

If an application is required in a newer version than available in the RealmJoin store, the same processes and rules apply as for the New Packages listed above. If the updated binary behaves exactly as the available version, command line parameters can be omitted in the request.

Note: Additional switches, new parameters or configuration files for an existing package are considered updates and shall be requested the identical way.

RealmJoin packaging request form

Tickets, Files and Setup

Please note that:

  • all requests need a file attached to be created successfully. Requests without any file upload are not submitted.

  • the request creates a ticket. All communication will be handled in this ticket, and it will only be sent to the account that created it. If this account does not have any active mailbox, the requester will not get any information.

  • the software requester role can be assigned to any user group in the tenant, therefore, an ADM account may not be required.

  • organic packages and PACKaaS might be not available right away, please get in touch with [email protected] if a feature is missing

Update and new package requests necessitate the provision of both binaries and documentation detailing the required command line parameters. If an update request does not entail changes from the previous version, the submission of new parameters is not required. All types of requests mandate a file upload, after which the generated ticket will be dispatched to the requesting account. Organic packages, offered at no cost, automatically extract the contents of the provided zip file to the C:\Install directory.

Last updated

Was this helpful?