Using WebLogic Integration - Business Connect
|
 |
 |
|
|
 |
 |
The following topics are provided about using WebLogic Integration - Business Connect applications.
Use this procedure to start the Administrator or Tracker application.
In a client-server configuration, start the Server application before you log on to Administrator or Tracker.
On some UNIX operating systems, occasional X windows scroll bar exceptions might occur in the normal use of the Administrator and Tracker X windows clients. These exceptions display in the terminal window where the clients were launched and are of no consequence.
Warning:
Name: HorScrollBar
Class: XmScrollBar
The specified scrollbar value is greater than the maximum
scrollbar value minus the scrollbar slider size.
On the Windows Start menu, select Programs
On UNIX, ensure you have X Windows connectivity to the system where WebLogic Integration - Business Connect is installed. Log in to the account you created during the installation process. Run the following command:
The Server application must be running before you can exchange documents with your partners. Although you can start and stop Server at any time, we recommend you run the application continuously.
We strongly recommended that you have only one instance of WebLogic Integration - Business Connect on a computer. You should not have two or more instances installed at the same time on the same computer. The only exception is when you temporarily have two instances installed while upgrading the application. But even in that case, you should not run two applications at the same time on the same computer.
The Server application synchronizes with your system's time for time-stamping transactions. If you change the system time on the system where the Server application is running, you must re-start the Server application for the Server to recognize the change.
If you are already running WebLogic Integration - Business Connect Server as a Windows service, you should not start it from your desktop.
On UNIX computers you can set up the Server application as a system service. See Installing WebLogic Integration - Business Connect.
The following topics are provided:
To start the Server application on Windows, select Start
After starting the Server application you can:
Figure 3-1 Server Display Window Transactions Tab
The following describes the fields on the Server Display window Transactions tab.
The action describing the transaction. Possible actions are:
The following describes the fields on the Server Display window Agents tab. An agent is a process that operates continuously or performs work when a specific event occurs.
The name of the agent. There are agents for the Server application itself and agents for transports, inbound polling, outbound polling, document packaging and unpackaging, document sending and receiving.
The agents for outbound and inbound polling show three numbers following each active transport or document type. These are, in order, the document polling rate in seconds, the documents per cycle and the maximum threads. The polling rate is the interval when WebLogic Integration - Business Connect polls for inbound or outbound documents. The documents per cycle is the maximum number of documents the application can retrieve at each polling interval. The maximum threads are packaging threads for outbound documents and unpackaging threads for inbound documents.
The status of the agent. The following are the possible status types.
|
The agent is packaging a document for sending to a partner. Depending on options you select, packaging can include encrypting, signing, MIME wrapping and compressing. |
|
|
The agent is running, but in a paused state. Paused indicates the Server application is waiting for memory to free up before continuing processing. Paused is a normal state for brief intervals. If this state persists, processing is exceeding available real memory. See Paused Server Processing. |
|
|
The agent is unpackaging a document received from a partner. Depending on selected options, unpackaging can include decrypting, decompressing and MIME unwrapping. |
|
|
The agent is attempting to connect to a transport server. Wait/connect is a normal state for brief intervals. If this state persists, it might indicate a transport failure. |
To start the Server application on UNIX, ensure you have X Windows connectivity to the system where WebLogic Integration - Business Connect is installed. Log in to the account you created during the installation process. Run the following command:
installation_directory/bin/start_server
In Administrator or Tracker, select Toolstail -f command to view the console output. (A Server Display window is not available on UNIX as it is on Windows.)
The following topics are provided for monitoring activity on the Server application.
You can use the View Server Log utility to view real-time activity on the Server application. The activity you view is recorded in the server.log file in the logs subdirectory under the directory where WebLogic Integration - Business Connect is installed. You can use the View Server Log utility only on the computer where you have installed the Server application. All Server actions display as they occur.
Note: If the View Server Log window is open when archiving occurs, the file you are viewing is archived and no further Server activity displays. When this occurs, the following line appears at the bottom of the window: Archiving console logs [date and time]. Open a new View Server Log window to continue monitoring activity.
On the Windows Start menu select Programsserver.log file. The server.log file is located in installation_directory\logs.
Figure 3-3 View Server Log Window
On UNIX, log in to the account you created during the installation process. Run the following command:
tail -f installation_directory/logs/server.log
To view a snapshot of all WebLogic Integration - Business Connect components, you can use the processes command. The output of this command identifies each WebLogic Integration - Business Connect process that is running. This can be helpful in troubleshooting the application. Run the following command:
installation_directory/bin/processes
For definitions of the column headings displayed with the processes command, use the man ps command.
Use this procedure to view Server application activity on a web page. You access the page with a browser such as Internet Explorer or Netscape Navigator that is on the same computer as WebLogic Integration - Business Connect Server or on a client computer with access to the Server. The Server application must be running for activity to display on the web page. The web page by default refreshes once a minute, but you can change the refresh rate.
The web page provides summary-level information not available in Tracker, such as totals for documents packaged, sent and received. It also shows whether server agents are active or idle and reports recent activity for transactions and alerts.
The information on the web page is for the current session of the Server application. If you stop and restart Server, the page display resets. You also can use the reset button to restart the counters in the summary section without restarting the application.
Alternately, to access the web page outside of Administrator or Tracker, open a browser and type a URL in the following format:
http://server_name:port_number/status/summary.html
Substitute the name of the computer running the Server application for server_name. The default port_number is 4080. If the computer name or port number has been changed, select Tools
Press Enter to display the web page.
Figure 3-4 Partial View of the Server Monitor Web Page
The following describes the information on the Server Monitor web page. To access the page, see Monitoring the Server with a Browser.
At the top of the page in the format [name] Server Monitor is the name under which the application is licensed. The name identifies whose trading activity the server monitor page is tracking. This is the name as it appears in the registered to field in Hel
You can view categories of information by clicking the links at the top of the page. The links are:
This area displays summary statistics about trading activity. The following information is in the Summary section.
Server running for [n] days, [n] hours, [n] minutes, [n] seconds
The elapsed time that Server has been running. The web page displays activity for the current session only. If you restart Server, the counters reset to zero. For historical trading information use Tracker.
The number of documents that have been packaged (encrypted and signed, as applicable) in the current session of Server. Packaging occurs before documents are sent to partners.
The number of acknowledgments or message disposition notices (MDNs) sent to trading partners to acknowledge receiving documents from them in the current session of Server.
The number of acknowledgments or MDNs received from trading partners in the current session of Server. Your partners sent the acknowledgments to acknowledge receiving documents from you.
The number of inbound or outbound documents that you or your trading partners have rejected in the current session of Server.
This area lists the status of Server agents. An agent is a process that operates continuously or performs work when a specific event occurs. This area displays data in three columns. The following describes the data in each column.
The first column is the name of the agent. There are agents for the Server application itself and agents for transports, inbound polling, outbound polling, document packaging and unpackaging, document sending and receiving.
The agents for outbound and inbound polling show three numbers following each active transport or document type. These are, in order, the document polling rate in seconds, the documents per cycle and the maximum threads. The polling rate is the interval when WebLogic Integration - Business Connect polls for inbound or outbound documents. The documents per cycle is the maximum number of documents the application can retrieve at each polling interval. The maximum threads are packaging threads for outbound documents and unpackaging threads for inbound documents.
The third column displays the status of the agent. The following are the possible status types.
|
The agent is packaging a document for sending to a partner. Depending on options you select, packaging can include encrypting, signing, MIME wrapping and compressing. |
|
|
The agent is running, but in a paused state. Paused indicates the Server application is waiting for memory to free up before continuing processing. Paused is a normal state for brief intervals. If this state persists, processing is exceeding available real memory. See Paused Server Processing. |
|
|
The agent is unpackaging a document received from a partner. Depending on selected options, unpackaging can include decrypting, decompressing and MIME unwrapping. |
|
|
The agent is attempting to connect to a transport server. Wait/connect is a normal state for brief intervals. If this state persists, it might indicate a transport failure. |
This area lists recent transactions in the current session of Server. For historical transaction information use Tracker. Transactions are displayed in the following format:
[company ID] [action] [document type or EDI control ID] [time and date]
The following describes each part of a transaction message.
The action describing the transaction. Possible actions are:
This area lists recent alert messages that have been generated in the current session of the Server application.
This area displays the summary, agents, transactions and alerts information on the same page. The page also displays the following two fields at the bottom.
This area lists the latest number of lines specified in the server.log file. To change the number of displayed lines, type the number in the number of lines to retrieve field and click Change.
Figure 3-5 Server Log Area of Server Monitor Web Page
Paused is a normal processing status for the Server application. The status can be reported in the agents table on the Server Monitor web page and on the Server Display window Agents tab on computers running Windows operating systems.
Paused indicates the Server application is waiting for memory to free up before continuing processing. Paused is a normal state for brief intervals. If this state persists, processing is exceeding available real memory. You have three options:
-mx[nnn]m, where [nnn] is half the real memory in megabytes on the computer running the Server application. You entered the computer's total amount of real memory when installing the application, and the system used half the amount as the [nnn] value. Only increase the -mx[nnn]m parameter value if your computer has enough memory and is not running other memory-intensive applications at the same time.On Windows the parameter is in the Server.bat and Server.ini files in the WebLogic Integration - Business Connect bin directory, and you must change the parameter in both files. On UNIX the parameter is in the WebLogic Integration - Business Connect bin/environment directory. Using a text editor, open the file, change the [nnn] value in the -mx[nnn]m parameter, save and close the file, and restart the Server application.
You can close and restart Administrator, Tracker and the Server application independently of each other.
You can close the Server application only on the computer where you have installed it and not from a client computer.
The following topics are provided.
To close the Server application on Windows, do one of the following:
To close the Server application on UNIX, log in to the account you created during the installation process. Run the following command:
installation_directory/bin/stop_server
If shutdown is successful, the following messages are displayed:
$ bin/stop_server
starting shutdown process ...
found local registry
found server
shutting server down ...
Server successfully shutdown.
Unlike the stop_server command, which only closes the Server application, the kill_app command on UNIX shuts down all WebLogic Integration - Business Connect processes. These include the Server, Administrator and Tracker applications. You might want to use this command only after trying other steps to resolve issues such as not being able to close or open Administrator or Tracker or having multiple Java processes running.
To use the kill_app command, log in to the account you created during the installation process and run the following command:
installation_directory/bin/kill_app
Select File
You can print a list of the records in the currently active information viewer by selecting File
The application prints the data as displayed on the current information viewer, so maximizing the window size before you print yields longer horizontal printed records. Although the records print in landscape format, you might have to adjust the column widths or hide columns of data in the information viewers to print the columns you want. This is necessary to account for differences in fonts and printers.
You can adjust column widths by placing the cursor over the lines between the columns headings to make a double-arrow appear. Click and hold the left button to adjust the widths. You also can click and drag columns headings to change their locations. You can hide or show columns of data by selecting View
The application prints the data as displayed on the current information viewer, so maximizing the window size before you print yields longer horizontal printed records. Although the records print in landscape format, you might have to adjust the column widths in the information viewers to print the columns of data you want. This is necessary to account for differences in fonts and printers.
You can adjust column widths by placing the cursor over the lines between the columns to make a double-arrow appear. Click and hold the left button to adjust the column widths. You also can click and drag columns to change their locations.
|
|
|