|
Testing the Web Application
Open a browser and write the directory path in the Address field (e.g. http://localhost:8080) or the port number you configured. If you have configured for port 80 is is enough with http://localhost. Of you are SSL you should instead try with https://localhost:8443 or https://localhost. The result should be as below:
Now you know that the web server works. If you now add /pipechain in the address field (e.g. http://localhost:8080/pipechain) or the name of your pipechain web application you should reach the login page.
In order
to be able to log on, the PipeChain Supply server must be running and
you must have linked a user to a supplier or partner. See the Workbook
for PipeChain WebAccess for Suppliers or Customers for more information.
SOAP
In order to use SOAP you need to open the MACom Channel Detail screen where you set up a new channel with the communication type SOAP. The only parameter you have to define is the “Used URI” where you enter http://[host]:[port number]/mywebapp/soap. Host meaning the IP address or host name of the web server.
When you perform a SOAP test you first connect and then send the transaction that is going to use the SOAP channel. Depending on how PipeChain SOAP has been configured in the servlet.properties, sending this transaction should create either a file or an entry in the receiving system’s PipeChain MACom Transaction Overview screen. You can for example connect the CS37 transaction with the SOAP channel and then press the Send Summed Suggestions button in the Own Business screen.
As a first test you can send a transaction from the PipeChain server, through PipeChain WebAccess back to your PipeChain server. Note that PipeChain will set the received transaction to Received Error, as the transaction will not be recognized as an incoming transaction.
A Note on Log Files
In the directory […]/ApacheTomcat40/logs there are log files that can be used to trace different events in the software. There are also files containing helpful information about Tomcat, e.g. trouble shooting. These are located in […]/ApacheTomcat40/webapps/tomcat-docs.