Pcc First Time User Try Again Error

Problem

After installing FileNet P8 5.0, opening the procedure Java applets returns a logon window then a "Failed to get configuration file WcmApiConfig.backdrop" error.

Symptom

When launching PCC the first time, a user logon prompt appears. When the user proper noun and password are provided the message "Failed to become configuration file WcmApiConfig.properties" is returned.

Cause

The Region Fundamental was not updated in Process Task Manager.

Surround

Windows Server 2008, Process Engine 5.0, Application Engine iv.0.2

Resolving The Problem

Check the post-obit:

1. Make sure a supported Java version is installed on the client machine beingness used to run the PE applets.
2. Make sure the version of the PE client is installed on the awarding engine matches the version of the Process Engine PE server.
3. Check the DNS proper name used in the PE Region ID referenced past the Connection Point and brand sure it returns the correct IP address of the PE or the virtual IP of the PE farm. This tin be done by opening a command prompt or console window and pinging the name referenced in the PE Region ID.
4. Update the region fundamental
1. Open Procedure Engine Process Chore Director and aggrandize the Regions folder and select the region having the problem.
2. Go to the Security Settings tab and check the "Update region cardinal" box. A list of the connection points defined in Content Engine Enterprise Director will appear.
3. Check the "Update" box for the connection point. Enter the user name and countersign that were defined when the associated PE Region ID was created and click Utilize.
   
4. Clear the Java cache on the client.

The applets should at present open normally, without displaying a login window. If the error persists, than the application server's session management and cookie handling is not setup properly. To resolve it, use the WebSphere Integrated Solutions Console to right the configuration.

5. Cheque for "com.ibm.ws.security.addHttpOnlyAttributeToCookies" in Security > Global Security > custom backdrop. If found, delete it.

6. Cheque for the custom property "com.ibm.ws.webcontainer.HTTPOnlyCookies" in Server > Server Types > WebSphere application servers > server_name > Web Container Settings > Web Container > Custom properties. If found, delete information technology.

7. Uncheck "Restrict cookies to HTTPS sessions" and "Set session cookies to HTTPOnly to help prevent cross-site scripting attacks" (only in WAS 8.ten) and check "Override session direction" at the application level. This has to be done in two places.

vii.1 Go to Applications > Application Types > WebSphere enterprise applications > Workplace XT > Modules >Manage Modules > WorkplaceXT > Session Management.

a. Under General Backdrop, cheque the box next to "Override session direction" and click Apply.

b. Enable cookies should be checked. Click the "Enable cookies" link in the Session tracking mechanism section.

c. Under General backdrop, verify that Cookie proper noun is set to JSESSIONID and uncheck "Restrict cookies to HTTPS sessions" and "Set session cookies to HTTPONly to help foreclose cross-site scripting attacks" (WAS 8.ten)

7.two Go to Applications > Application Types > WebSphere enterprise applications > Workplace XT > Spider web Module Properties >Session Direction.

a. Under General Properties, check the box next to "Override session management" and click Apply.

b. Enable cookies should be checked. Click the Enable cookies link in the Session tracking mechanism section.

c. Nether General backdrop, verify that the Cookie name is prepare to JSESSIONID and uncheck "Restrict cookies to HTTPS sessions" and "Set session cookies to HTTPONly to help prevent cantankerous-site scripting attacks" (WAS 8.x) and click Utilize.

8. For WebSphere Application Sever eight.0.0.ten and above, disable HTTP Only settings globally for SSO. (See Running P8 Client Applications with WebSphere Application Server 8.0.0.10 for details)


Notation: This step is required for all Workplace XT deployments. Skip this footstep for Workplace (Application Engine), unless yous are using SSO or a Container Managed configuration.

a. Navigate to Security > Global security > Authentication > Spider web and SIP security > Single sign-on (SSO).

b. Nether Full general properties, uncheck "Set security cookies to HTTP Only to assistance prevent cross-site scripting attacks" and click Apply

ix. Enable cookies and disable HTTP Only settings at the server level setting when using SSL.

a. Navigate to Servers > Server Types > WebSphere application servers.

b. Select the server where Workplace/Workplace XT is deployed.

c. Click Session Direction.

d. Click the Enable cookies link under Session tracking machinery.

eastward. Uncheck "Set session cookies to HTTP Simply to assistance prevent cantankerous-site scripting attacks".

10. Save the changes to the master configuration and restart WebSphere. If the application is running in a cluster, all nodes and the deployment manager must exist restarted.

11. Articulate the Java enshroud at the browser level and through the Java console on the clients running the applets.

The applets should now launch normally, without displaying a login window.

Related Data

[{"Product":{"code":"SSTHRT","characterization":"IBM Case Foundation"},"Concern Unit":{"code":"BU053","label":"Deject & Data Platform"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF027","label":"Solaris"},{"lawmaking":"PF033","label":"Windows"},{"code":"PF016","characterization":"Linux"},{"lawmaking":"PF010","characterization":"HP-UX"}],"Version":"5.0;5.1.0","Edition":"All Editions","Line of Business":{"code":"LOB45","label":"Automation"}}]

holdenardess.blogspot.com

Source: https://www.ibm.com/support/pages/opening-ibm-filenet-process-configuration-console-pcc-returns-failed-get-configuration-file-wcmapiconfigproperties

Share this post