InterWorx

Connect InterWorx to WISECP to manage SiteWorx hosting accounts and track their disk and traffic usage through service records.

Accessing the Screen

Open Products → Servers → Add New Server; choose InterWorx under Server Automation Module. Edit existing records from the Servers list.

Before You Start

You need a working, licensed InterWorx server and a NodeWorx administrator API key. The key must allow SiteWorx account management, package reads and IP listing. WISECP needs the PHP SOAP extension and access to the NodeWorx SOAP endpoint.

Prepare package templates and an available hosting IP in NodeWorx before provisioning. The module chooses the first free IP; it does not purchase another address. Saved servers also have Preferences, Linked Services and Import. Sales require an active server and a hosting product priced in your chosen currency.

Connection and Product Settings

Tasks

Connecting NodeWorx

1. Complete Connection Details and click Test Connection in the server summary.
2. The test reads available IPs. Check success and complete Identity and Capacity. Success alone does not confirm a free IP or account-write permission.
3. Click Add New Server and check the list entry. Editing uses Save Changes.

Mapping a Package

1. Open the hosting product's Automation → Module Assignment and select InterWorx.
2. Under Server Configuration, choose Single Server or Server Group. Select Module Configuration → Package.
3. Check Resource Limits and configure product prices. Package selection does not import products or synchronize provider prices.
4. Keep the first product hidden with Automatic Setup disabled. Click Save Changes; check its package and server selections.

Package storage is MB; monthly traffic is GB and converts to MB in WISECP. Zero or empty package limits mean unlimited. Mailbox, MySQL, FTP, subdomain, secondary-domain and pointer-domain counts are mapped. Hourly email has no package counterpart.

One service creates one SiteWorx account for its domain, using the customer's email, a username and a password. No saleable add-ons or order requirements are generated. The module has no specific add-on actions.

Linking Existing Accounts

1. On a saved server, click Import → List Results. The module reads account domains and resolves their usernames.
2. Check duplicate domains and missing usernames. Select accounts and map each customer, product, billing cycle and dates.
3. Click Import below the list. Check Linked Services; the existing SiteWorx account is linked without being recreated.

Managing SiteWorx Services

Open an existing test service's Management → Overview to compare disk and traffic gauges with SiteWorx. Creation, suspension, unsuspension, termination, password and package changes are supported. Use the dialogs in Service Management.

Under Management → Settings → Package, select another package and click Save Changes; package limits are reapplied. Product upgrades also apply the chosen package. Leaving the new package empty does not clear the existing panel package.

Customers open the service's Management tab. Panel access submits the customer email, stored service password and domain to SiteWorx. It is not a single-use token. Imported accounts need matching email and password for automatic login; the import list does not retrieve passwords.

Outside a service context, the login link opens the manual SiteWorx login page. WISECP has no separate file, email, database, FTP, DNS, cron, SSL or PHP tools for this module. Manage them inside SiteWorx. Check access on an existing test service before enabling automatic setup.

Disk and traffic usage can feed billing metrics. Periodic collection does not synchronize prices or change panel quotas. Configure usage prices separately; enabled billing can add charges.

Things to Watch

Required Permissions

Server settings require MODULES_SERVERS_SETTINGS; product editing requires PRODUCTS_OPERATION. Service operations need their respective service permissions.

Related Articles

• Adding a Server
• Product Automation
• Server Groups