Skip to content
pCon.configurator onlineDocumentation
Esc
↑↓navigate↵open⌘Jpreview
On this page

Verify the Installation

Verify the complete environment after OFML Data Setup and after upgrading the installation. A running service is the first check; the catalog and article checks confirm that the data is usable as well.

Check services and licenses

On Windows, open Services and confirm that OCF_Licenseserver and OCF_EAIWS are running. On Linux, run:

systemctl status eails.service
systemctl status eaiws.service

Both Linux services should report active (running). Review the latest logs in the EAILS and EAIWS var/log directories. On Windows, these are <installPath>\pCon\EAILS\var\log and <installPath>\pCon\EAIWS\var\log, where <installPath> is the destination configured in config.xml. Resolve license, Java, plugin or startup errors before proceeding.

Check installed data and configuration

  1. Confirm that the DataClient update completed successfully.
  2. Check that the configured catalogs/profiles directory and, when used, catalogs/default.profiles registration file exist under the chosen data destination.
  3. Confirm that the EAIWS service account can read the data and session start-up file.
  4. Check that the client uses the intended startup configuration: the default is session.cfg; custom filenames require the -startup option.

Test a session, catalog and article

Use your application’s EAIWS client or a SOAP client configured for your installation’s endpoint:

  1. Call openSession with the intended startup configuration. It should return a session ID without a fault.
  2. Call listCatalogItems with that session ID and an empty catalog path. Confirm that the expected manufacturer catalogs are returned.
  3. Browse a catalog to a known article and insert it using insertOFMLArticle. Use identifiers from the installed data.
  4. In your integrating application, check that the article’s properties can be displayed and a supported configuration change can be applied.
  5. Close the test session with closeSession.

Use a known configurable article for the last check. The available catalogs, articles and properties depend on the installed manufacturer data.

Troubleshooting

Symptom Check
A service fails to start Service logs, Java 21, required libraries, file permissions and plugin setup.
Session creation fails License availability, startup filename and configuration, and the EAIWS log.
Expected catalogs are missing DataClient result, selected data destination, registration file, profile selection and service-account read access.
Newly installed data is not visible Update-script startup-file refresh step and the configuration selected by a newly opened session.
An article cannot be inserted or configured The selected article’s data, required plugins and licenses, and the returned fault and EAIWS log.

For further administration, see Configuration, Licensing and SSL Setup.