3.4.1 WebSphere node name
The node name in WebSphere is case sensitive. This is relevant when you start the console with AdminClient and when you specify an IIOP address for a JNDI lookup (for example, within the batch files which start client programs). It is also relevant to tools such as the XML export or import utility.
Usually the name is entirely in lowercase. However, on some systems, it is entirely in uppercase and could, in theory, be a mixture of both.
If you find that the console fails to start with such messages as "Could not get attributes" (similar to when the service/subsystem is not started), but the service is started, then the case of the name may be the problem.
You can verify the required name by using the following SQL to look at a WebSphere table:
select NAME
from EJSADMIN/NODE_TABLE
This shows the node name exactly as WebSphere wants it. Do not be tempted to change the contents of this table. It is liable to make things worse rather than better. (You need to have QSECOFR authority to read this table.)
3.4.2 Errors on starting the client
Verify that there are no tabs or spaces after any of the parameters in standard.properties, particularly if using the CCClient method where these are set up manually.
With data errors, once you sign on to the call.connect GUI, verify that advanced pricing is switched on for the company in use.
Also check that the search family code is set up in the OM company profile.
3.4.3 Errors when running the client
If pricing, tax, or discounting does not work correctly, check that the library list for the job description used by OMUSER is correct.
If amended data does not appear, for example an OM item specification that is newly setup, delete the .bl object in the log folder (see the following section). If you still have problems, stop and start the beans in WebSphere to update the cached data.
3.4.4 Cached data and .bl and .cd files
To make call.connect as fast as possible, data from more stable files is cached in WebSphere. If these files change, the new data will not be available to call.connect until the application server is stopped and restarted. The following information is cached:
User profiles as held in /OrderManagement/log/UserDirectory.xml
System21 company profiles
In addition, buying list and customer data is held in files in the /OrderManagement/log folder. These files are of type .bl and .cd respectively. These files are normally updated by the System21 options on menu /OMP, Generate Buying Lists and Call List Generation. You may delete the files if necessary, for example, for testing purposes.
54Geac System21 commerce.connect: Implementation on the iSeries Server
