================================================= == == == IBM(R) WebSphere(R) Premises Server == == version 6.1.0.1 == == Software Interim Fix - APAR IC59101 == == README == == == ================================================= CONTENTS -------- 1.0 ABOUT THIS README FILE 2.0 INCLUDED IN THIS INTERIM FIX 3.0 INSTALLATION 4.0 UNINSTALLATION 5.0 TRADEMARKS 1.0 ABOUT THIS README FILE -------------------------- This README provides information about the patch available in this interim fix. This fix can be installed on IBM WebSphere Premises Server version 6.1.0.1. 2.0 INCLUDED IN THIS INTERIM FIX -------------------------------- The following reported program defects are fixed in this update: o IC59101: Premises Server iFeature Container Tracking sample use case updates 3.0 INSTALLATION ----------------- 3.1 Prerequisites o It is assumed that WebSphere Premises Server is already installed. o It is assumed that WebSphere Premises Server 6.1 Feature Pack for Sensor Event Services and the WebSphere Premises Server 6.1 Feature Pack for Sensor Event Services Toolkit is already installed. 3.2 Installation Procedure 1. Unpack the IC59101.zip file. 2. Apply this fix as described in the technote "Updating EAR files for WebSphere Premises Server" technote, available at: http://www.ibm.com/support/docview.wss?rs=3467&uid=swg21326858 The IC59101.zip file contains files IBMPremisesRUC.ear, IBMPremisesRUCBackendImpl.ear, and IBMPremisesRUCUseCase.ear. When applying this fix in WebSphere Application Server, update the applications "ibmruc_rucimpl_ear," "ibmruc_backendimpl_ear," and "IBM_Container_Tracking_Use_Case," respectively. 3. If using the WebSphere Premises Server 6.1 Feature Pack for Sensor Event Services Toolkit, import all projects from the project interchange ibmct_source.zip file, which is in the IC59101.zip file, into the workspace. Also, copy files IBMPremisesRUC.ear and IBMPremisesRUCUseCase.ear to \iFeature in the workspace folder and follow the toolkit instructions to configure the server profile. 4. Create activation apecifications for IBMCTTagReadAS: a. Open the WebSphere Application Server administrative console. b. Select Resources > JMS > Activation specifications. c. FOr scope, select Node=PremisesNode,Server=server1. d. Click New. e. Select Default messaging provider and click OK. f. Enter the following values and then click Apply > OK. i. Name: IBMCTTagReadAS ii. JNDI name: eis/IBMCTTagReadAS iii. Destination type: Topic iv. Destination JNDI name: jms/ibmse v. Message Selector: ibmse='RfidInventory/TagReport' OR ibmse='RfidInventory/TagAggregationReport' OR ibmse LIKE '%/report/TagReport' OR ibmse LIKE '%/report/TagAggregationReport' vi. Bus name: ibmsensorevent 5. Create the com.ibm.premises.ct.bizlocation property in the WebSphere Premises Administrative Console. a. Open the WebSphere Premises Server Administrative Console. b. Click Agent Configuration. c. Click SystemAgent. d. Click com.ibm.premises.SystemAgent. e. Select Add Property. f. Enter the following information: i. Name: com.ibm.premises.ct.bizlocation ii. Value: Enter an identifier for the location where Container Tracking is running. g. Click Update PID. h. Click Update (click OK if a popup appears). i. Exit the WebSphere Premises Server Administrative Console. 6. Restart WebSphere Application Server 4.0 UNINSTALLATION ------------------- Refer to the "Updating EAR files for WebSphere Premises Server" technote, available at: http://www.ibm.com/support/docview.wss?rs=3467&uid=swg21326858 5.0 TRADEMARKS ---------------- IBM and WebSphere are registered trademarks of International Business Machines Corporation in the United States, other countries, or both. (C)Copyright IBM Corporation 2004, 2008. All Rights Reserved. Note to U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.