Framework Terminology
Message – The files sent and received through Framework are called messages. A message contains one or more documents.
Document – A document is typically an individual business document, i.e., an order or invoice. The Eliassen Framework is designed to processes documents individually.
Rules – Eliassen’s B2B Framework provides default rules to process data. You can create custom rules to modify the default handling, or to provide processing for certain cases.
Rules Engine – Framework includes a Management Interface to create, modify, and delete the rules used for processing messages and documents.
Rules Tables – Framework uses tables of rules to control the processing of messages and documents. Business Processes access these tables to find the rule that best matches their requirements.
Mailboxes – Framework can collect messages from or deliver messages to mailboxes.
Portal – Framework’s browser-based user interface.
Framework operates using its own database, and shares information with the B2Bi database as well.
Framework’s core functionality is composed of:
• Reprocessing and resending of documents and messages (Document Visibility)
• Rules and maps (Framework Management)
• Visibility (Document Visibility)
• Reports (Custom Reports)
• User profiles (Administration)
Starting The Portal
Framework does not require any special steps to start when B2B Integrator is started. However, Portal runs in a separate JVM and must be started separately after Integrator is running. Additionally, if you have enabled SSO, the External Identity Provider must be running as well. If the Portal cannot reach the External Identity Provider, it will not start. To start the Portal, follow these steps:
Using a command line tool, navigate to the <installDirectory>/Portal directory. Run the following command:
• Linux/Unix With A Service
◦ systemctl start lightwell-portal
• Linux/Unix Without A Service
◦ java –jar portal-api.jar &
• Windows With A Service
◦ Open the "Services" menu
◦ Find the "Lightwell Portal" service
◦ Select service and click "Start"
• Windows Without A Service
◦ javaw -jar portal-api.jar
When the Portal is ready for use, the command line will return a message, “Settings successfully pulled and web server started.” Close the command window and open your browser to http://<B2BIserver>:PortalPort. Remember that the Portal port is recommended to be 680 ports higher than your B2BI base installation port. Example: if the B2BI base installation port is 10000, the url for Portal would appear as:
Stopping The Portal
Framework does not require any special steps to stop when B2B Integrator is stopped. However, Portal runs in a separate JVM and does not stop when you stop the B2B Integrator system. To stop the Portal:
• Linux/Unix With A Service
◦ systemctl stop lightwell-portal
• Linux/Unix Without A Service
◦ Use the grep function to locate pid, and the kill command to stop the process.
▪ ps aux | grep portal-api
▪ Look for java –jar portal <pid>
▪ kill <pid>
• Windows With A Service
◦ Use the Task Manager to locate and end the process.
▪ The process will appear as java
▪ Click this process to select it
▪ Click End Task
• Windows Without A Service
◦ Open the "Services" menu
◦ Find the "Lightwell Portal" service
◦ Select service and click "Stop"
Comments
Post a Comment