Start all package names with an uppercase letter and capitalize the first letter of subsequent words (for example, PurchaseOrder).

Keep package names short. Use abbreviations instead of full names. For example, instead of ProcessPurchaseOrder, use ProcessPO.

Make sure the package name describes the functionality and purpose of the services it contains.

Avoid creating package names with random capitalization (for example, cOOLPkgTest).

Avoid using articles (for example, “a,” “an,” and “the”) in the package name. For example, instead of TestTheService, use TestService.

Do not use the prefix “Wm” in any case combination. Integration Server and Designer use the “Wm” prefix for predefined packages that contain services, IS document types, and other files. Additionally, custom packages with a “Wm” prefix can be problematic when deploying the packages using Deployer.

Avoid using control characters and special characters like periods (.) in a package name. The watt.server.illegalNSChars setting in the server.cnf file (which is located in the IntegrationServer_directory\instances\instance_name\config directory) defines all the characters that you cannot use when naming packages. Additionally, the operating system on which you run the Integration Server might have specific requirements that limit package names.