Access

Lynda Autocad Plant 3d Essential Training- Admin [work] May 2026

For professionals taking the AutoCAD Plant 3D Essential Training: Admin course (formerly on LinkedIn Learning

), several critical whitepapers and guides can supplement the video instruction. Top 5 Administrative Whitepapers

These highly recommended papers address technical areas covered in the course, such as project configuration and database management: Autodesk Community, Autodesk Forums, Autodesk Forum De-mystifying AutoCAD Plant 3D Isometrics

A deep dive into the engine that generates isometric drawings. Managing Large Projects

Insights on organizing large-scale projects into cohesive entities for better reporting and multi-user performance. External Database Reference Manager Guide

Essential for administrators linking Plant 3D projects to external database sources. Database and Configuration Management:

Technical documentation on managing the underlying database processes that support the user interface. Project and Specification Configuration:

Practical insights for setting up catalogs and custom specs, which is a core skill for any admin. Autodesk Community, Autodesk Forums, Autodesk Forum Essential Companion Guides ASCENT Piping Guidebook Often recommended for newcomers, the Introduction to Plant Design

book provides clear exercises that parallel basic admin setup guidelines. Official Course Exercise Files: If you have a LinkedIn Learning subscription , always download the Exercise Files

tab directly on the course page. These contain the actual project templates and sample data used in Irene Radcliffe's lessons. Key Admin Topics Covered in the Training

To stay organized while studying, focus your reading on these "paper-heavy" administrative tasks: Project Setup: Creating custom project and drawing properties. Data Manager: Customizing views and generating engineering reports. Catalogs & Specs:

Building and modifying component libraries outside of the drawing environment. Report Creator:

Configuring the standalone tool for bill of materials and custom report outputs. customizing isometric templates AI responses may include mistakes. Learn more AutoCAD Plant 3D Essential Training: Admin Online Class

Lynda AutoCAD Plant 3D Essential Training- Admin: A Comprehensive Guide

Are you an administrator looking to streamline your plant design workflow with AutoCAD Plant 3D? Look no further! Lynda's AutoCAD Plant 3D Essential Training- Admin is a comprehensive course designed to help administrators master the essential skills needed to manage and customize AutoCAD Plant 3D for their organization's specific needs.

What is AutoCAD Plant 3D?

AutoCAD Plant 3D is a powerful plant design software that allows users to create detailed 3D models of plant equipment, piping, and structures. It's widely used in the process plant, oil and gas, and power generation industries to design and manage complex plant projects. Lynda AutoCAD Plant 3D Essential Training- Admin

What does the course cover?

In this course, administrators will learn the essential skills needed to manage and customize AutoCAD Plant 3D. The course covers the following topics:

Setting up and configuring AutoCAD Plant 3D: Learn how to install, configure, and customize AutoCAD Plant 3D for your organization's specific needs.
Managing project settings and standards: Understand how to manage project settings, standards, and specifications to ensure consistency across your plant designs.
Creating and managing catalogs and libraries: Learn how to create and manage catalogs and libraries to customize the software's component data and ensure accuracy.
Administering user access and security: Understand how to manage user access, permissions, and security settings to ensure data integrity and control.
Integrating with other Autodesk software: Learn how to integrate AutoCAD Plant 3D with other Autodesk software, such as AutoCAD and Navisworks.

Key Takeaways

By completing this course, administrators will gain a solid understanding of how to:

Configure and customize AutoCAD Plant 3D for their organization's specific needs
Manage project settings, standards, and specifications
Create and manage catalogs and libraries
Administer user access and security
Integrate AutoCAD Plant 3D with other Autodesk software

Who should take this course?

This course is ideal for:

Administrators responsible for managing and customizing AutoCAD Plant 3D
IT personnel responsible for supporting plant design software
Plant design managers looking to improve their team's workflow and productivity
Anyone interested in learning about AutoCAD Plant 3D administration

Conclusion

Lynda's AutoCAD Plant 3D Essential Training- Admin is a comprehensive course that provides administrators with the essential skills needed to manage and customize AutoCAD Plant 3D. By completing this course, administrators will be able to streamline their plant design workflow, improve productivity, and ensure data integrity. Whether you're new to AutoCAD Plant 3D administration or looking to refresh your skills, this course is a great resource to help you succeed.

Get started today!

Enroll in Lynda's AutoCAD Plant 3D Essential Training- Admin course today and start mastering the essential skills needed to manage and customize AutoCAD Plant 3D for your organization's specific needs.

Mastering the Backend: A Review of AutoCAD Plant 3D Essential Training: Admin

For any piping professional, moving from a standard user to a project administrator is a major career milestone. While the "User" side of the software is about creating models, the Administrator role is about building the world those models live in. I recently dove into the AutoCAD Plant 3D Essential Training: Admin

course on LinkedIn Learning (formerly Lynda.com) led by industry expert Irene Radcliffe

. Here’s a breakdown of why this course is a must-watch for anyone looking to control their project environment rather than just working within it. The Role of the Admin

The course starts with a critical truth: the success of a 3D plant project often hinges on the setup. As an administrator, you aren't just "drawing"; you are managing the project databases, tool palettes, and data integrity. Radcliffe frames the Project Manager interface as the "brains" of the operation—the central hub where all customization happens. What You’ll Learn Clocking in at roughly 5 hours and 21 minutes

, this intermediate-level course covers the heavy lifting of project configuration: Project Setup & Configuration: For professionals taking the AutoCAD Plant 3D Essential

Learn to create new projects from scratch or templates, define project paths, and lock properties to maintain standards. Class Definitions & Tagging:

This is where the "intelligence" happens. You’ll learn how to create custom equipment and valve tag formats so your data is consistent across the entire facility. Drawing Customization:

Beyond the 3D model, the course covers how to set up drawing templates for orthographics and customize isometric styles, including bill of materials (BOM) layouts. Data Management: One of the most powerful sections covers the Report Creator

. You’ll learn how to generate engineering reports directly from your 3D data, saving hours of manual data entry. Who Is This For?

This isn't a "getting started with AutoCAD" course. It’s specifically designed for: Existing Plant 3D Users who want to control configuration settings. CAD Managers responsible for maintaining company standards. Senior Designers

looking to improve their software proficiency and move into leadership roles. Why Take It? 4.8/5 rating

from hundreds of learners, the consensus is clear: the instruction is "very helpful and clear". Radcliffe focuses on methodologies and naming conventions that don’t just make you a better drafter, but make the entire project more profitable by ensuring efficiency and accuracy from day one. Final Verdict:

If you’re tired of "broken" projects and manual workarounds, taking the time to master the administrative side of Plant 3D is the best investment you can make this year. If you'd like, I can provide more details on: Specific course chapters or time breakdowns for each topic Next-step courses to take after finishing the Admin module Hardware requirements recommended for running Plant 3D efficiently AutoCAD Plant 3D Essential Training: Admin Online Class

The LinkedIn Learning course "AutoCAD Plant 3D Essential Training: Admin," led by Irene Radcliffe, provides 5 hours and 21 minutes of instruction on managing, configuring, and maintaining project files. The training covers project initialization, database configuration, custom property creation, and generating reports using the Report Creator tool. Explore the full course on LinkedIn Learning. AutoCAD Plant 3D Essential Training: Admin Online Class

Here’s a professional social media post tailored for LinkedIn, Facebook, or a company training group. You can adjust the tone based on your audience (e.g., more technical vs. more motivational).

Post Title: Master the Backend of AutoCAD Plant 3D with "Essential Training: Admin" by Lynda (LinkedIn Learning)

Post Body:

🛠️ Stop fighting your software. Start managing it like a pro.

If you're responsible for deploying, customizing, or maintaining AutoCAD Plant 3D in your organization, the "Lynda AutoCAD Plant 3D Essential Training: Admin" course is your new blueprint.

This isn't just another "how to draw a pipe" tutorial. It's designed for the Project Managers, CAD Managers, and Lead Designers who need to:

✅ Set up & manage project standards – From spec-driven design to report configurations. ✅ Configure the user interface & tool palettes – Streamline workflows for your entire team. ✅ Master Project Setup & Data Management – Avoid broken links, missing specs, and project corruption. ✅ Automate tedious admin tasks – Save hours of manual cleanup and troubleshooting. Setting up and configuring AutoCAD Plant 3D :

💡 Why this matters: A well-administered Plant 3D environment reduces errors, enforces consistency across teams, and cuts down project rework by up to 30%.

Whether you're migrating from 2D, standardizing across multiple sites, or just tired of being the "IT guy" for Plant 3D issues — this course gives you the control you need.

🎯 Who should watch?

CAD/BIM Administrators
Plant Design Leads
Engineering Managers
Anyone responsible for Plant 3D project templates & specs

🔗 [Link to course – insert your Lynda/LinkedIn Learning link here]

Have you already taken this course? What’s your biggest admin headache in Plant 3D right now? Drop a comment below 👇

#AutoCADPlant3D #PlantDesign #CADAdministration #Lynda #LinkedInLearning #PDMS #EngineeringDesign #CADManagement

P&ID Integration (The Admin Link):

The most valuable 20 minutes of the course involves AutoCAD P&ID integration. You learn to:

Map a P&ID line tag (100-P-101-6"-A1A) to a 3D model line.
Validate that the 6" pipe in 3D matches the 6" pipe on the P&ID.
Generate a "Line Number Conflict" report to catch designer errors before fabrication.

Data Integrity

The training highlights the connection between the 3D model and the project database. This ensures that reports (such as line lists, equipment lists, and BOMs) are always up-to-date with the visual model, reducing discrepancies between the drawing and the data.

2) Detailed checklist for an admin-focused evaluation

Technical prerequisites
- Software versions required
- Hardware and OS recommendations
Installation & deployment
- Does the course show centralized deployment or MSI/automated install options?
- Network/Client-server setup guidance (Project Data Server, shared folders)
Project templates & standards
- Creation/management of company templates and project setup best practices
- Standards (P&ID, piping specs, catalogs)
Data management
- Project data storage locations, backups, and recommended folder structures
- Integration with Vault or other document management systems
User, role & permission management
- How to create/manage users and roles
- Access control for projects and files
Collaboration & multi-user workflows
- Setting up multi-user projects, conflict resolution, referencing workflows
- Best practices to minimize data corruption and version conflicts
Customization & automation
- Admin-level customization: templates, parts catalogs, spec files
- Scripting, macros, or API usage coverage (Plant 3D .NET or other automation hints)
Troubleshooting & maintenance
- Common issues, recovery steps, log locations, and repair workflows
Security & backup
- Recommended backup schedules, restore testing, offsite strategies
- Any mention of encryption, network security, or access logging
Training & user onboarding
- Does the course provide materials for training end users (slides, exercises, datasets)?
Enterprise considerations
- Scalability, multi-site setups, version control strategy, support/SLAs

Ideal Candidate for Training

This course is best suited for:

Experienced AutoCAD users transitioning into process plant design.
Drafters who need to move from 2D general drafting to 3D specialized modeling.
Engineers who want to understand the capabilities and limitations of the software to better manage design teams.

3. Project Setup and Configuration

Who Should Take This Course?

Not every CAD user needs to watch the "Admin" track. You should invest the 4–6 hours into this Lynda course if you are:

The CAD Manager: You need to roll out Plant 3D to a department of 20 drafters. You need templates.
The Project Lead: You are responsible for delivering the "Digital Twin" to the client. You need to ensure data integrity.
The Solo Engineer: You are a one-person team designing a small plant. Doing it wrong the first time will cost you weeks of re-modeling.
The IT Support Specialist: You need to understand why Plant 3D is crashing (hint: it is usually a network latency or write-permission issue in the Project XML files).

Who is this course actually for?

Let’s clear this up immediately. This is not for the casual drafter.

If you are the person everyone yells at when “the spec won’t load” or “the isometrics look weird,” this course is your survival guide. It is designed specifically for the Project Administrator—the user who sets up projects, manages catalogs, and builds the specification sheets.

The Verdict

Rating: 4.8/5 Instructor: [Insert Instructor Name] (Clear, methodical, and mercifully avoids industry jargon without explanation).

Pros:

Focuses on high-ROI admin tasks.
Excellent section on data management (Copy/Move projects).
Works for both the 2023, 2024, and 2025 versions (concepts are stable).

Cons:

Slightly dry in the middle (XML editing is never exciting, but it is necessary).
Could use a downloadable "dirty" project file to practice fixing broken specs.

Configuring the XIMSS Module

Use the WebAdmin Interface to configure the XIMSS module. Open the Access page in the Settings realm:

Use the Log setting to specify the type of information the XIMSS module should put in the Server Log. Usually you should use the Major (message transfer reports) or Problems (message transfer and non-fatal errors) levels. But when you experience problems with the XIMSS module, you may want to set the Log Level setting to Low-Level or All Info: in this case protocol-level or link-level details will be recorded in the System Log as well. When the problem is solved, set the Log Level setting to its regular value, otherwise your System Log files will grow in size very quickly.

The XIMSS module records in the System Log are marked with the XIMSSI tag.

When you specify a non-zero value for the Maximum Number of Channels setting, the XIMSS module creates a Listener. The module starts to accept all XIMSS connections that clients establish in order to communicate with your Server. The setting is used to limit the number of simultaneous connections the XIMSS module can accept. If there are too many incoming connections open, the module will reject new connections, and the client should retry later.

By default, the XIMSS module Listener accepts clear text connections on the TCP port 11024. Follow the Listener link to tune the XIMSS Listener.

XIMSS Connections to Other Modules

XIMSS connections can be made to TCP ports served with other CommuniGate Pro modules. If the first symbol received on a connection made to the HTTP module is the < symbol, the HTTP module passes the connection to the XIMSS module.

When a connection is passed:

the logical job of the passing module completes.
the logical job of the XIMSS module is created, in the same way when an XIMSS connection is received on a port served with the XIMSS module.
the XIMSS module restrictions for the total number of XIMSS channels and for the number of channels opened from the same IP address are applied.

When all users initiate XIMSS connections via other Module ports, you can disable the XIMSS Listener by setting all its ports to zero.

XIMSS Sessions

When a user is authenticated, the XIMSS module creates a XIMSS session. The current XIMSS module TCP connection can be used to communicate with that session.

A XIMSS session can be created without the XIMSS module, using special requests sent to the HTTP User module. See the XIMSS Protocol section for more details.

The XIMSS session records in the System Log are marked with the XIMSS tag.

HTTP Binding

A client application can access the XIMSS interface via HTTP connections.

A client application should start by sending an HTTP Login request to create a new XIMSS session.

When a XIMSS session is created, the client application can send XIMSS protocol requests to it and receive XIMSS protocol responses from the session using HTTP requests.

Client applications can use GET and POST HTTP requests.
If a request contains a body, it is assumed to be an XML text, unrelated to the actual value of the Content-Type header field. The XML text must be a <XIMSS/> element.
If a request produces a non-empty response body, the body is always an XML text containing one <XIMSS/> element, and the response Content-Type header field is text/xml.

Open the HTTP User Module settings, and find the Sub-Protocols panel:

The Access setting specifies who can create XIMSS sessions using HTTP Binding.

HTTP Login

To start a XIMSS session, a client application should send an HTTP request to the CommuniGate Pro HTTPU module using the following URLs:

http://domainName[:port]/ximsslogin/
or
https://domainName[:port]/ximsslogin/

If the request contains the userName parameter, the Server tries to authenticate the specified user (Account):

If the password parameter is present, the regular clear-text method is used.
If the nonce parameter is present, the CRAM-MD5 method is used. The "nonce" parameter value should be a value received as part of a features response (see below), it should be a valid "authentication nonce". The request must contain the authData parameter containing the base64-encoded CRAM-MD5 "challenge response".
If the sessionid parameter is present, the SessionID method is used.
If the errorAsXML parameter is present and the login operation fails, the error condition is returned not as an HTTP result code with an HTML error page, but as an <response/> element with errorNum and errorText attributes, enclosed into a <XIMSS/> element.
If the version parameter is present, its value specifies the protocol version the client implements (see the Login operation parameters).

If the userName parameter is absent, the Server tries to authenticate the request using the TLS Client Certificate (if specified), or using the HTTP authentication methods.
This functionality is the same as the WebUser Interface Automatic Login and Single Sign-on functionality, but the /ximsslogin/ URL is used.

A request to the /ximsslogin/ URL can contain a text/xml body. In this case, no login operation is performed.
The XML body should contain one <XIMSS> element containing zero, one, or several XIMSS Pre-Login operations. The Server sends an HTTP response with XML data. The response is a <XIMSS> element containing the requested operations result.

Example:

C:GET /ximsslogin/ HTTP/1.1
  Host: myserver.com
  Content-Type: text/xml
  Content-Length: 42

  <XIMSS><listFeatures id="list" /><XIMSS>

S:HTTP/1.1 200 OK
  Content-Length: 231
  Connection: keep-alive
  Content-Type: text/xml;charset=utf-8
  Server: CommuniGatePro/5.3

  <XIMSS><<features id="s" domain="x.domain.dom"><starttls/><sasl>LOGIN</sasl><sasl>PLAIN</sasl><sasl>CRAM-MD5</sasl><sasl>DIGEST-MD5</sasl><sasl>GSSAPI</sasl><nonce>2C3E575E5498CE63574D40F18D00C873</nonce><language>german</language><signup/></features><response id="s"/></XIMSS>

If the user has been successfully authenticated, and the XIMSS session has been created, the HTTP Login response contains the XIMSS session message with the session ID string. Note that the session message does not contain the id attribute.

Example:

C:GET /ximsslogin/?userName=account@domain&password=abcd&version=6.1 HTTP/1.1
  Host: myserver.com
  Content-Length: 0

S:HTTP/1.1 200 OK
  Content-Length: 105
  Connection: keep-alive
  Content-Type: text/xml;charset=utf-8
  Server: CommuniGatePro/5.3

  <XIMSS><session urlID="562-kAI2lxNBR4ApmHg4wiW9" userName="account@domain" realName="J. Smith" version="6.1.2" /></XIMSS>

Alternative URLs can be used to start a XIMSS session using the TLS Client Certificate, or using the HTTP authentication methods:

http://domainName[:port]/auth/ximsslogin/
or
https://domainName[:port]/auth/ximsslogin/

This method is useful if an application first retrieves an HTML page or some other document using the /auth/ realm, forcing the browser to ask the user for credentials, and then the application creates a XIMSS session for the same user, as the browser will resend the same credentials when sending a request to the /auth/ximsslogin/ URL.

HTTP Synchronous Communications

A client should send requests to a created XIMSS session use the following Session URL:

http://domainName[:port]/Session/sessionID/sync
or
https://domainName[:port]/Session/sessionID/sync

where sessionID is the session message urlID attribute.

The HTTP request body should contain one <XIMSS /> element, with zero, one, or more XIMSS protocol requests.

The Server returns one <XIMSS /> element in the HTTP response body. This element contains the XIMSS protocol response messages (one for each XIMSS request sent, in the same order), and all synchronous data messages generated with the submitted XIMSS requests.

Example:

C:POST /Session/562-kAI2lxNBR4ApmHg4wiW9/sync HTTP/1.1
  Host: myserver.com
  Content-Length: nnn

  <XIMSS><noop id="i1" /><readTime id="i2" /></XIMSS>

S:HTTP/1.1 200 OK
  Content-Length: nnn
  Connection: keep-alive
  Content-Type: text/xml;charset=utf-8
  Server: CommuniGatePro/5.3

  <XIMSS><response id="i1"/><currentTime id="i2" gmtTime="20070502T083313" localTime="20070502T003313"/><response id="i2"/></XIMSS>

If a XIMSS client works in an unreliable environment, where it may have to resend HTTP requests, then each non-empty HTTP request should contain a reqSeq parameter. This parameter value should be increased by 1 for each new HTTP request sent.
If the Server receives an HTTP request with the same reqSeq parameter as the previously received and processed HTTP request, then the Server resends the last response (one it has sent to the previous HTTP request wit the same reqSeq).
If the Server receives an HTTP request with the reqSeq parameter not equal to the reqSeq parameter of the previously received request and not equal to the reqSeq parameter of the previously received request increased by 1, then the Server returns an error.

A client application can use an "empty request" (an HTTP request without a body) to read asynchronous XIMSS data messages.

When such an empty request is received, the Server checks if there is any pending asynchronous data messages for the specified session. If there is no pending asynchronous data messages, the request is held until either:

an asynchronous data message is generated for the session; or
the waiting time is over; or
a new "empty request" is received; or
the session is closed.

An empty request can specify the waiting time as the maxWait parameter (number of seconds).

If no data messages were retrieved, the Server sends a response containing an empty <XIMSS/> element, without any attributes.

If some data messages were retrieved, the Server sends a response (an "asynchronous response") containing one <XIMSS/> element, with the respSeq attribute. This attribute contains the sequence number for this <XIMSS/> response element.

For each session, the Server keeps the last "asynchronous response" composed.

Each empty request should contain a ackSeq parameter. It should contain the respSeq value of the last received asynchronous response.
If the client has not received any asynchronous response yet, this parameter value must be 0.

When the Server receives an empty request with the ackSeq equal to the respSeq value of the kept last composed asynchronous response, it considers that response as "acknowledged", and removes it.

When the Server receives an empty request with the ackSeq equal to the respSeq value of the last composed asynchronous response minus one (respSeq-1), and it still keeps this composed response, the Server resends that response to the client. As a result, if the client encounters any communication error while doing an "empty request" HTTP transaction, it can resend that empty request.

An empty request without an ackSeq parameter acknowledges all "asynchronous responses" composed and kept.

When a server returns an empty <XIMSS/> element, the next empty request can contain either no ackSeq parameter, or the same ackSeq parameter as the previous empty request. Because of this subsequent empty requests may use the same request URL and the same parameters, and the client platform may return the previous cached <XIMSS/> element result immediately, without sending the request to the server.
To avoid this problem, include the reqSeq parameter into each empty request, increasing its value after a successful transaction.

Example:

C:GET /Session/562-kAI2lxNBR4ApmHg4wiW9/get?maxWait=90&ackSeq=0&reqSeq=0 HTTP/1.1
  Host: myserver.com
  Content-Length: 0

...optional pause (up to 90 seconds)...
S:HTTP/1.1 200 OK
  Content-Length: 10
  Connection: keep-alive
  Content-Type: text/xml;charset=utf-8
  Server: CommuniGatePro/5.3

  <XIMSS/>
C:GET /Session/562-kAI2lxNBR4ApmHg4wiW9/get?maxWait=90&ackSeq=0&reqSeq=1 HTTP/1.1
  Host: myserver.com
  Content-Length: 0

...optional pause (up to 90 seconds)...
S:HTTP/1.1 200 OK
  Content-Length: nnn
  Connection: keep-alive
  Content-Type: text/xml;charset=utf-8
  Server: CommuniGatePro/5.3

  <XIMSS respSeq="1"><folderReport folder="INBOX" mode="notify" /></XIMSS>
response did not reach the client, client is resending the request
C:GET /Session/562-kAI2lxNBR4ApmHg4wiW9/get?maxWait=90&ackSeq=0&reqSeq=1 HTTP/1.1
  Host: myserver.com
  Content-Length: 0

S:HTTP/1.1 200 OK
  Content-Length: nnn
  Connection: keep-alive
  Content-Type: text/xml;charset=utf-8
  Server: CommuniGatePro/5.3

  <XIMSS respSeq="1"><folderReport folder="INBOX" mode="notify" /></XIMSS>
C:GET /Session/562-kAI2lxNBR4ApmHg4wiW9/get?maxWait=90&ackSeq=1&reqSeq=2 HTTP/1.1
  Host: myserver.com
  Content-Length: 0

...optional pause (up to 90 seconds)...
S:HTTP/1.1 200 OK
  Content-Length: 10
  Connection: keep-alive
  Content-Type: text/xml;charset=utf-8
  Server: CommuniGatePro/5.3

  <XIMSS/>

HTTP Asynchronous Communications

A client can send requests to a created XIMSS session so that all responses (including the response messages and synchronous data messages) are returned only in response to the "empty requests".

http://domainName[:port]/Session/sessionID/async
or
https://domainName[:port]/Session/sessionID/async

where sessionID is the session message urlID attribute.

The HTTP request body should contain one <XIMSS /> element, with zero, one, or more XIMSS protocol requests.

All generated response messages (one for each XIMSS request sent, in the same order), and all synchronous data messages generated with the submitted XIMSS requests are re-submitted to the XIMSS session as asynchronous messages. The Server returns an empty HTTP response.

Example (single connection, polling):

C:GET /Session/562-kAI2lxNBR4ApmHg4wiW9/get?maxWait=0&ackSeq=0&reqSeq=0 HTTP/1.1
  Host: myserver.com
  Content-Length: 0

S:HTTP/1.1 200 OK
  Content-Length: 10
  Connection: keep-alive
  Content-Type: text/xml;charset=utf-8
  Server: CommuniGatePro/5.3

  <XIMSS/>
C:POST /Session/562-kAI2lxNBR4ApmHg4wiW9/async HTTP/1.1
  Host: myserver.com
  Content-Length: nnn

  <XIMSS><noop id="i1" /><readTime id="i2" /></XIMSS>
S:HTTP/1.1 200 OK
  Content-Length: 0
  Connection: keep-alive
  Content-Type: text/plain;charset=utf-8
  Server: CommuniGatePro/5.3

C:GET /Session/562-kAI2lxNBR4ApmHg4wiW9/get?maxWait=0&ackSeq=0&reqSeq=1 HTTP/1.1
  Host: myserver.com
  Content-Length: 0

S:HTTP/1.1 200 OK
  Content-Length: nnn
  Connection: keep-alive
  Content-Type: text/xml;charset=utf-8
  Server: CommuniGatePro/5.3

  <XIMSS respSeq="1"><response id="i1"/><currentTime id="i2" gmtTime="20070502T083313" localTime="20070502T003313"/><response id="i2"/></XIMSS>

Example (2 connections, waiting):

C:GET /Session/562-kAI2lxNBR4ApmHg4wiW9/get?ackSeq=0&reqSeq=0 HTTP/1.1
  Host: myserver.com
  Content-Length: 0

...waiting...

S:HTTP/1.1 200 OK
  Content-Length: nnn
  Connection: keep-alive
  Content-Type: text/xml;charset=utf-8
  Server: CommuniGatePro/5.3

  <XIMSS respSeq="1">
    <response id="i1"/>
    <currentTime id="i2" gmtTime="20070502T083313"
      localTime="20070502T003313"/>
    <response id="i2"/>
  </XIMSS>
C:GET /Session/562-kAI2lxNBR4ApmHg4wiW9/get?ackSeq=1&reqSeq=1 HTTP/1.1
  Host: myserver.com
  Content-Length: 0

...waiting...

C:POST /Session/562-kAI2lxNBR4ApmHg4wiW9/async HTTP/1.1
  Host: myserver.com
  Content-Length: nnn

  <XIMSS><noop id="i1" /><readTime id="i2" /></XIMSS>
S:HTTP/1.1 200 OK
  Content-Length: 0
  Connection: keep-alive
  Content-Type: text/xml;charset=utf-8
  Server: CommuniGatePro/5.3

Monitoring XIMSS Activity

You can monitor the XIMSS Module activity using the WebAdmin Interface.

Click the Access link in the Monitors realm to open the Access Monitoring page:

3 of 3 selected

ID	IP Address	Account	Connected	Status	Running
9786	[216.200.213.116]	user1@domain2.dom	3min	listing messages	2sec
9794	[216.200.213.115]	user2@domain1.dom	34sec	reading request
9803	[216.200.213.115]		2sec	authenticating

ID: This field contains the XIMSS numeric session ID. In the CommuniGate Pro Log, this session records are marked with the XIMSS-nnnnn flag, where nnnnn is the session ID.
IP Address: This field contains the IP address the client has connected from.
Account: This field contains the name of the client Account (after successful authentication).
Connected: This field contains the connection time (time since the client opened this TCP/IP session).
Status: This field contains either the name of the operation in progress or, if there is not pending operation, the current session status (Authenticating, Selected, etc.).
Running: If there is an XIMSS operation in progress, this field contains the time since operation started.

XIMSS activity can be monitored with the CommuniGate Pro Statistic Elements.