Microsoft Dynamics 365 Finance and Operations (D365FO) leverages Application Object Servers (AOS) to handle user requests and execute business logic. In environments with multiple AOS instances, user sessions are typically distributed dynamically based on workload balancing. This flexibility ensures optimal resource utilization. However, there are scenarios where you might need to pinpoint your user session to a specific AOS.

This blog post delves into the concept of pinning your user session to a specific AOS in D365FO. We’ll explore the use cases that necessitate this approach, the steps involved in achieving it, and the potential implications.

Understanding User Sessions and AOS Distribution

D365FO operates on a client-server architecture. When a user logs in to the application, a session is established with an available AOS instance. This AOS handles the user’s requests, retrieves data, and executes relevant business logic.

The system employs a load balancer to distribute user sessions across multiple AOS instances. This ensures that no single AOS becomes overloaded, maintaining optimal performance throughout the system.

When Does Pinning Become Necessary?

While dynamic session distribution offers performance benefits, there are situations where pinning becomes advantageous:

1. Troubleshooting and Debugging: Imagine you’re troubleshooting an issue specific to a user’s session. You might need to enable tracing (a logging mechanism) on the user’s AOS instance to capture detailed information about their actions and system interactions. If the session is dynamically distributed, tracing becomes challenging as you wouldn’t know which AOS to target. Pinning allows you to focus the trace on the specific AOS where the user’s session currently resides.
2. Security Auditing: In certain security audits, you might need to analyze the actions performed by a specific user within the system. Pinning the user’s session ensures that the audit trail reflects activity on the designated AOS, simplifying the analysis process.
3. Customization and Development: During development or customization activities, you might require a controlled environment for testing code changes. Pinning your session to a specific AOS guarantees that your development activities occur within a predictable and isolated instance, preventing unintended impacts on other users.

How to Pin Your User Session to a Specific AOS

While D365FO doesn’t offer a direct user interface option for pinning sessions, it can be achieved through manipulation of the application pool configuration on the server hosting the AOS instances. Here’s a general outline of the steps involved:

1. Identify the Target AOS Instance:

• Use server administration tools to access the server hosting the AOS instances.
• Locate the application pool(s) associated with the D365FO AOS instances. Information about application pools can typically be found in server management consoles like Internet Information Services (IIS) Manager.

2. Modify the Application Pool Configuration:

• Right-click on the application pool representing the target AOS instance you want to pin to.
• Select “Advanced Settings” from the context menu.
• Locate the setting named “Session Affinity (Enabled)”.
• Change the value to “true”.

3. Restart the Application Pool:

• Once “Session Affinity (Enabled)” is set to “true”, it’s crucial to restart the application pool for the changes to take effect.

4. Launch Your User Session:

• With the target AOS application pool configured for session affinity, launch your D365FO user session. The system will now attempt to direct your session specifically to that AOS instance.

Important Considerations:

• Pinning a user session can potentially impact performance, particularly in environments with limited AOS resources.
• Avoid pinning sessions for regular use cases as it disrupts the load balancing strategy, potentially leading to uneven resource utilization across AOS instances.
• Remember to revert the “Session Affinity (Enabled)” setting to “false” after completing your troubleshooting, debugging, or development activities.

Additional Notes:

• The specific steps for accessing and modifying application pool settings might vary depending on your server environment and operating system.
• It’s recommended to consult with your D365FO system administrator for guidance on implementing these changes in your specific environment.

Conclusion

Pinning your user session to a specific AOS in D365FO serves a valuable purpose in specific scenarios like troubleshooting, security auditing, and controlled development environments. By understanding the use cases and the steps involved, you can leverage this technique effectively for targeted analysis and development activities. However, remember to exercise caution and only utilize pinning when necessary to avoid impacting overall system performance and load balancing.

---

For those looking to fortify their Project development team or seeking expert assistance in building secure applications, Bizcommits is here to help. With a team of skilled developers and a proven track record of delivering secure and scalable solutions, we can be your trusted partner in the ever-evolving realm of application Development. Ready to discuss your project? Contact us today!