FPSAPP.SCH_C_HOSTS

FACILITY

VARCHAR2(6)

Facility is included in almost every join in the DWH so this represents a definitive split. A route must have all steps on tools in the same facility. A tool must process all lots in the same facility. If your site has multiple buildings where lots run on routes using tools in multiple buildings then everything should be one facility. For example, multiple Fab buildings. But if your site has independent facilities like Fab and Test and Assembly where lot may progress from one to the next but on different routes then these should be different facilities. Since this column is in virtually every table it is critical that the value here is exactly matches what is in the MES if the MES has facility. Use facility_display for the display friendly name displayed in applications. See site_name comment for client/site/facility example. (* from FPSINPUT.GEN_FACILITIES)

HOST_ID

VARCHAR2(50)

DATABASE_NAME

VARCHAR2(256)

The database to which this host is relevant

APP_POOL

VARCHAR2(50)

This is the application pool that the application should be run under

HOST_ACTION

VARCHAR2(100)

Indicate the default action of host

HOST_CONTROLLER

VARCHAR2(100)

Indicate the default controller of host

HOST_DESC

VARCHAR2(500)

HOST_TYPE

VARCHAR2(36)

is used to tell if this is for WEB or SERVICE (* from FPSAPP.SCH_C_GROUP_HOSTS)

HOST_URL

VARCHAR2(500)

PRELOAD_REFRESH_ACTION

VARCHAR2(100)

Indicate the action for the data refresh

PRELOAD_REFRESH_CONTROLLER

VARCHAR2(100)

Indicate the controller for the data refresh

RECYCLE_URL

VARCHAR2(500)

URL which points to the application that will recycle the application pool

RESULT_REFRESH_ACTION

VARCHAR2(100)

Indicate the action when it needs to send the signal that the new result is ready

RESULT_REFRESH_CONTROLLER

VARCHAR2(100)

Indicate the controller when it needs to send the signal that the new result is ready

WALLET_PATH

VARCHAR2(256)

Path to the Oracle wallet for https calls, for example file:/ORACLE/wallet