Skip to Main Content
Return to Navigation

Troubleshooting Tracking Data Issues

This topic provides recommended solutions to one of the more common issues encountered by PeopleSoft Enterprise Learning Management (ELM) customers. It discusses how to resolve issues associated with:

Note: Do not construe the information provided here as consulting or implementation advice for your specific industry or your individual organization. You should adapt or disregard this information based on the needs of your organization. Oracle does not guarantee that the information included here will work as intended within your customized environment.

Separate Communication and ELM Servers

Some customers set the Communication Server for L&T option to a server that is separate from the ELM web server. In this situation, you must ensure that tracking information, such as completion status or score, is written to the ELM database.

To ensure that tracking information is written to the ELM database, first, try setting the Communication Server for L&T option to the same server and port as the ELM web server. Once this simple scenario works, set the Communication Server for L&T option to another web server and port that is configured to communicate with the ELM application server.

Note: There is currently a documented issue with using a port number on the second server that's different than the ELM web server number. Until this issue is resolved, set the port numbers on your ELM application server and Communication server to the same value.

Separate Communication Server and ELM Server Ports

Some customers set the Communication Server for L&T option to a different port than the ELM server. One issue that can arise with this configuration is that course tracking data does not make it to the ELM database.

PeopleTools clarified that the behavior observed with the single web server and two WebLogic domains is working as designed. The course tracking data issue has more to do with the way that the Microsoft Internet Explorer browser functions. Because both servers are running on the same machine, the cookies created by the first server are automatically shared with the second server. To prevent this sharing and to enable both course tracking and the ability for learners to log in to the application from an email link, we suggest two options.

Both options provide a way to avoid the sharing of cookies. Both PeopleTools and ELM support teams will fully support either option. Please note that the following options are also applicable to load-balanced environments.

  • Option 1: Two physical web servers.

  • Option 2: One physical web server running two WebLogic domains on two separate ports.

Option 1 has these advantages:

  • Performance

  • Redundancy

  • Long-term stability (insulation from any possible inconsistencies).

Option 2 requires some network manipulation. You can give your web server machine two domain names in the DNS server in order to differentiate the two URLs from one another. You'll need to add a DNS name for the second web server for port 7003 so that all the URLs for this port will use this new name instead of the original name of the first web server. Adding a new name ensures that the browser will not share cookies, and you will not see the course tracking data issue.

Alternatively, you can recreate the web server running on port 7003 to include the domain name. In other words, instead of http://<web_server_name>:7003, you would use a URL similar to this: http://<web_server_name>.peoplesoft.com:7003. Using this alternative web address should prevent the browser from sharing cookies as well.

The advantage of Option 2: Because Option 2 uses the same web server, it is less expensive than Option 1. The disadvantages of Option 2:

  • If the whole web server goes down, both sites go down.

  • More configuration effort is involved.

  • Potential for volatility exists due to software changes.