Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. What's New in Informatica Intelligent Cloud Services
  3. API Center
  4. Administrator
  5. Application Integration
  6. Business 360 Console
  7. Cloud Data Integration for PowerCenter (CDI-PC)
  8. Data Access Management
  9. Data Governance and Catalog
  10. Data Ingestion and Replication
  11. Data Integration
  12. Data Integration Connectors
  13. Data Quality
  14. Data Validation
  15. MDM - Customer 360 SaaS
  16. MDM - Product 360 SaaS
  17. MDM - Reference 360
  18. MDM - Supplier 360 SaaS
  19. Multidomain MDM SaaS
  20. Monitor

What's New

What's New

Process Server restart

Process Server restart

As part of this release, updates were made to the Process Server service on the Secure Agent. The updates do not affect the service and the agent processes will continue to work as is. As a result of the deployment of the updates, you will see that the status of the Process Server service shows up as
Restart Required
.
If you have configured an upgrade restart schedule for the Process Server, the restart will happen automatically as per the schedule. Otherwise, by default, the restart will happen 7 days after your Point of Deployment (POD) upgrade.
If you would like to manually restart the Process Server at your own convenience and get the latest updates, perform the following steps:
  1. Open the Administrator service and select
    Runtime Environments
    .
  2. On the
    Runtime Environments
    page, click the name of the Secure Agent.
    You might have to expand the Secure Agent group to see the list of Secure Agents within the group.
  3. Click the
    Details
    tab.
  4. In the
    Agent Service Start or Stop
    area, select the service as
    Process Server
    .
  5. Click
    Stop
    .
  6. Click
    Start
    to restart the Process Server service. After the service starts, the status changes to
    Up and Running
    . If the service fails to start, check the audit log to find the cause of the error.
For more information about Secure Agents, see
Runtime Environments
in the Administrator help system.

0 COMMENTS

We’d like to hear from you!