In case the application doesn't work as expected, you might try the following:
|
Problem
|
Possible solution
|
|
The Tomcat service registration fails with an error.
|
Make sure to run the service registration as local administrator.
Make sure no other Tomcat with the same service name is already installed.
Don't use blanks in the Tomcat service name.
|
|
Tomcat doesn't start.
|
Take a look at the Tomcat log files in <PIM_SUPPLIER_PORTAL_INSTALLATION_ROOT>/tomcat/logs
Make sure that the configured ports are not in use. You can change the ports in <PIM_SUPPLIER_PORTAL_INSTALLATION_ROOT>/tomcat/conf/server.xml.
Depending on the local configuration, Tomcat might not have sufficient rights to open ports. Run the Tomcat service as an appropriate user in this case.
Make sure to use the right JDK for Tomcat. You can set the JDK using the Windows Tomcat service by opening the file <PIM_SUPPLIER_PORTAL_INSTALLATION_ROOT>/configure.bat. Choose the tab Java and check the JVM Settings:
|
|
Tomcat starts but the webapp doesn't.
|
Take a look at the Product 360 - Supplier Portal log files in <PIM_SUPPLIER_PORTAL_INSTALLATION_ROOT>/logs or at Tomcat log files in <PIM_SUPPLIER_PORTAL_INSTALLATION_ROOT>/tomcat/logs
Test the database connection.
Check if the database tables have been created. If not, run the script again and look for errors.
Test the Product 360 - Server connection. Product 360 - Supplier Portal doesn't start if Product 360 - Server cannot be reached. If Product 360 - Server runs but Product 360 - Supplier Portal reports an error, take a look at the Product 360 - Server logs.
Make sure that the configuration.properties file and its properties are valid. Please keep in mind, that every 'properties' file (ending with *.properties) will be read and all contained properties will be imported (e.g. if you have a copy of the configuration.properties file which also ends with *.properties and its properties are changed, this could lead to unpredictable property values of the Product 360 - Supplier Portal system).
If you activated password encryption by using the tag [_to_encrypt_] (see: Encryption of secure information) the included JRE in <PIM_SUPPLIER_PORTAL_INSTALLATION_ROOT>/jre have to support strong AES-256 cryptographic algorithm. This can be easily done and is described here: Usage of AES-256 cryptographic algorithm. Otherwise a RunTimeException occurs which contains: 'Key length (256 bit) is greater than the max allowed key length (128 bit)'.
|
|
The URL in the browser results in a 404 error message.
|
|
|
There's a spring error in the logs saying that table XYZ is missing.
|
Open the Product 360 - Supplier Portal log file to check if the database setup succeeded and all migrations have been applied. Errors related to "flyway" usually point to a failed database setup.
Ensure that the database user has the necessary permissions.
|
|
I changed a configuration property but it doesn't work.
|
|
|
SocketException occurs on Product 360 - Supplier Portal server if many Product 360 - Supplier Portal clients are active.
|
Increase the number of sockets in the windows registry using RegEdit.exe:
Add key: MaxUserPort with the value 65534 in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
see also in:
|
|
Tasks cannot be created/assigned to suppliers, i.e. the "Supplier" option is available as assignee in the task creation dialog.
|
Make sure that the following settongs in the hsx.properties of the Product 360 server are set as follows:
hsx.enabled = true
hsx.suppliertasks.enabled = true |
|
Tasks for suppliers (Task node "Tasks assigned to suppliers") are neither displayed in Desktop nor Web client.
|
Make sure that the access right "Show tasks for all suppliers" is granted to the respective user group/organization.
|