Asset Suite / PassPortGeek

Portal/RF general discussion.
Portal/RF is thought to be obsolete. Not sure when.
AnyWare for Inventory (formerly IndusAnyWare) does not use Portal/RF, but is instead very similar to Portal/J in TCP mode.
Ref: AWI_IG.pdf, page 3: AWI is client software which consists of a set of different components running on different hardware platforms. Users access AWI from their handheld computer / Portable Data Terminal (PDT). The PDT is used primarily as a data input and viewing device; it is connected via wireless network connection to a Microsoft Windows Terminal Server. The main application software is a Java Applet that runs on the Terminal Server. The AWI Applet uses Portal/J TCP mode communications to communicate with the PassPort host computer, and it also relies on the Portal/J web server for access to configuration information, cached resources, and other data.

Use the URL alias icon, data dictionary element TIG16061, to invoke a Java servlet and have the .ccp panel program know when the web browser has been closed (URL-TRANSFER-IN-PROGRESS-COM(STACK-TOP-COM)). Define the URL alias on X108 to be something like: http://server:port/fixml/servlet/servSomething? to use a Java servlet that you've defined to the Indus FI Connect product.

The FI Connect product is providing a lot of services for you to use like database access (servlet code: Connection dbconn = PPUtil.getDbConnection();), and a working directory (servlet code: String workdir = PPSAPConfig.getDocumentDirectory() + "/work";).

Note that this is a one-way invokation of the servlet, that is, it's possible to send parameters to the servlet, but not possible to send data back to the .ccp program. The servlet could update a database table that the .ccp would read, similar to the way IndusBuyDemand processes a shopping cart.

The actual JRE that will load on a PC when it first accesses PassPort is retained on the Portal/J server in a directory similar to ../tomcat/webapps/PJ/plugin. It is the actual JRE executable from Sun.
The JRE that Portal/J will run with is specified on the Portal/J server in a directory similar to ../tomcat/webapps/PJ/html/runtime, file PJPanelFrame.html. Look for "codebase". It's possible to change the JRE version to match a version installed on a PC that is not on the Portal/J server. This can be useful for debugging. It actually occurred with Portal/J 9.2 that originally was certified with JRE version 1.4.1 which had a problem with ATI RADEON video card drivers. Sun acknowledged the problem (bugs 4713003 and 4749817) and fixed it in JRE 1.4.2.