Middleware for integration connects different subsystems or modules to a large integrated landscape. In this way, it becomes possible to increase the efficiency and quality of work across different applications. This is usually done based on an automated interface.
TPG PSLink® is a worldwide leading product for integration and bidirectional data exchange between systems for project management, collaboration, work management and ERP. Thus, the product integrates different environments used at the company in general – however mainly in the project context.
Frequently Asked Questions for TPG PSLink
Answers to common questions regarding TPG PSLink middleware have been compiled in this list.
“The Microsoft PPM solution with a great deal of individual customizing by TPG provides comprehensive scheduling, resource and cost planning tailored to our processes. Thanks to the integration with SAP, the cost overview in Microsoft Project Server is always complete and up to date.”
Eduard B. Bleckmann, Senior PMO Manager, KARL STORZ SE & Co. KG
Answers to common questions regarding integration with TPG PSLink.
TPG PSLink supports all current versions of SAP including HANA.
TPG PSLink supports the Atlassian Jira on-premises version as well as the cloud-based version.
Yes, TPG PSLink lets you integrate SAP directly with Atlassian Jira and other systems. Microsoft Project is not a prerequisite.
The TPG PSLink architecture is designed to provide all the basic functions (such as login and logging) within the framework itself. The connectors then provide the link to other systems and handle specialized use cases. There are connectors for software such as Microsoft Project, SAP (for several use cases), Atlassian Jira, Microsoft TFS / DevOps, SharePoint, Primavera, and others.
No, you do not need to program any SAP functions. The TPG PSLink connectors use standard SAP functional components. If necessary, TPG PSLink can be used to launch a customer’s own programs from within SAP.
No, TPG PSLink does not directly access the SAP database. The two systems communicate only via functional components.
Yes, TPG PSLink can be integrated with Project Online in the cloud as well as the following versions of Microsoft Project Server: 2013, 2016 and 2019.
Yes, this is possible in most cases. It requires that your time recording system has one of the following connectivity options: SQL, Webservice, REST or File Exchange.
You can launch the data exchange either manually, or automatically in accordance with a preset schedule such as nightly, weekly or monthly. Workflows and other events can also be used to trigger this. For example, events such as saving a project or publishing a project in Microsoft Project Server / Project Online can also be used as triggers.
Yes, you can set up load balancing in environments with traffic involving numerous resources.
The server components of TPG PSLink are installed on the Windows Server as a service or in the IIS. The installation can be done on a Windows Server on-premises or an Azure environment. There is also a web client and a Microsoft Project client add-in that can be used as needed, depending on the use case.
No, we stopped supporting this scenario many years ago. TPG PSLink only supports solutions involving Project Server / Project Online. This is to ensure data consistency because there can be any number of copies of the MPP files.
You can either purchase TPG PSLink or choose a subscription plan. The price of each is determined by the number of users and the connectors needed for your use cases.
Yes, you can configure the synchronization processes in TPG PSLink (PSLink jobs) to be restricted to specific user roles. These roles can be, for example PMO, controller or project manager.
Yes, TPG PSLink can be integrated with any SAP module from SAP R/3, ECC or SAP S/4HANA. The most common are PS, CO, PM, FI, SD, MM, HR, IM, CATS, and BI/BW.
Yes, the data exchange is generally bidirectional. Often the integration is actually multi-directional. For example, you can have a scenario in which data is transferred first from SharePoint to SAP, and then from SAP to the Microsoft Project Server, and from there finally to Atlassian Jira.
No, the principal system depends on the use case. For example, SAP can be the principal system for creating the project and Microsoft Project for the structure matching. This can even be configured at the field level: project attributes are the determinant in SAP, for example, whereas in Microsoft Project it is the project deadline. The other integrated systems behave similarly.
Of course, it is theoretically possible to develop a solution in-house. However, this is very expensive and time-consuming. In the long run, it is more difficult and time-consuming to maintain a solution developed in-house than a standardized product. For example, every time one of the integrated systems is updated, you will need to spend time updating the in-house solution. This requires having staff with the necessary expertise to do this.
The advantage of using a product is that the developer always updates the product to the newest system version to keep it future-proof.
Our experience has shown that the costs over the product’s lifetime are much lower than for solutions developed in-house.
Yes, TPG PSLink has been SAP certified as an “Integration SAP Application” since 2009. Microsoft has granted the product the status “Windows Server Certified”. Both certifications are regularly renewed.
TPG PSLink has been designed to use native APIs (integration interfaces from the product vendors) to read and write data. We currently support the PPM solution Microsoft Project Server / Project Online, Planisware Enterprise and Orchestra and TPG ProjectPowerPack based on the Microsoft Power Platform.
TPG PSLink has built-in support for web services, Odata queries and PowerShell. All of them can be used to integrate Microsoft Dynamics e.g. CRM or Project for the Web (which is using Dynamics for data storage).
TPG PSLink is fully integrated into the user interface i.e. integration jobs can be started from the menu in an open project and the user is informed about job execution and the result. Also, the history of all integration jobs is visible, per project and across all projects.