Why Does Isadc.sh Fail to Upload Files
Data Collector for the Content Engine, Process Engine, and Rendition Engine components of IBM FileNet Content Manager 5.two.ten
The IBM FileNet Content Director 5.2.x Data Collector automates the problem-reporting information collection tasks for the Content Engine, Process Engine, and Rendition Engine components of the Content Managing director five.two.x and Content Platform Engine five.2.x products.
This data collector can be run on whatsoever platform on which the Content Director five.2.x or Content Platform Engine 5.ii.x software has been installed (Windows, Linux, AIX, Solaris, HP Integrity, or HP Risc).
This information collector makes it easy to gather the basic data nearly your IBM FileNet Content Director five.two.x server when you need to submit information for apply with a PMR or defect study.
ICM 5.2.ten users will use this data collector in the event of ICM issues involving the Content Engine, Process Engine, or Rendition Engine.
Running this data collector will not automatically enable any traces. Depending upon the problem beingness seen, information technology might be advisable to first enable some tracing and reproduce the problem so run the data collector. But, you tin can e'er create and get together traces after.
ISADC is an applet running in the browser. This information collector gathers the log, trace and configuration files from the machine directly. The ISA Data Collector must be run on the server on which the needed diagnostic data is located. For this information collector, you will run the data collector on the server where the IBM FileNet Content Manager v.2.10 software is installed and running.
When running the IBM FileNet Content Manager v.ii.10 data collector, you should exist logged on to the IBM FileNet Content Manager v.ii.x server nether the user that installed the IBM FileNet Content Manager 5.2.x software or the user that is running the IBM FileNet Content Director 5.2.x software.
If the user who is running the information collector does not take appropriate admission to the things that need to be collected, the collector volition non exist able to successfully collect everything that is required.
For example, when collecting the Process Engine data, the data collector must be run while logged on as a user who has enough privileges to
Running the Data Collector in a Spider web Browser on an IBM FileNet Content Manager 5.2.x Server Connected to the Internet
| 1 |
 |
| 2 | If yous do not have a suitable java plugin installed for your spider web browser, follow the prompts to get a java plugin installed. |
| three | The ISA Data Collector GUI initiates in the web browser: |
| 4 | Click the + to view the data collector scripts located within the IBM FileNet Content Manager 5.2.x folder |
At this signal, you are ready to run any of the data collector scripts that are listed. Each script will ask different questions and collect unlike data. Details of each data collector script are discussed beneath.
Once the data has been collected by a particular script, the data collector will consummate with the following 2 questions:
| 1 | When the data drove has completed, you'll exist prompted with an opportunity to provide feedback on the data collection experience. Select i of the options: |
| two | Then, you are given a chance to FTP the gathered information directly to IBM. Select one of the options: If you want, you lot can select Practise Non Transfer and expect at exactly what has been nerveless and manually upload the data later. |
| three | The collector is washed. If y'all selected Do Non Transfer in the previous pace, the actual name and location of the goose egg file containing the collected data volition appear on the data collector screen: |
Running the Data Collector Without a GUI or While Non Continued to the Internet
If, for some reason, you cannot y'all can not direct run the ISADC collector in a web browser on the IBM FileNet Content Manager 5.2.x server while connected to the internet, there are provisions for downloading a zip file, unzipping it, and running the downloaded data collector using a script/batch file in a command prompt window or using an html file in your web browser.
| ane | Download the Data Collector
 |
| ii | Copy the Data Collector zip file to the IBM FileNet Content Platform Engine five.2.x server If, in the previous footstep, you did non download the ISADC collector cypher direct to the IBM FileNet Content Platform Engine 5.2.x server, you must now re-create the ISADC data collector naught file to the IBM FileNet Content Platform Engine 5.two.10 server. For case, for a Unix-based IBM FileNet Content Platform Engine 5.2.10 server, you might use FTP to "put" the simply-downloaded ISADC zip file to the /tmp directory on the server. |
| 3 | Unzip the data collector Unzip the information collector zip file (or .tar.gz file) into the directory where you lot volition run it. The unzip operation will create a folder chosen isadc. The ISADC data collector tin can be run from any directory. Hint: on a Unix box, with the downloaded isadc data collector zero file in the /tmp folder, in a command prompt, doing something similar to the following volition unzip the data collector: |
| 4 | In a control prompt window, cd into the isadc folder that you just unzipped. For example, cd \isadc or cd /tmp/isadc. |
| v | Make Unix/Linux script executable If your IBM FileNet Content Platform Engine five.2.x server is Unix-based (AIX, Linux, HP, or Solaris), in the directory where you unzipped information collector nil file (e.chiliad., /tmp/isadc), make the scripts executable by running this command: |
| half dozen | Fix up JAVA_HOME environment variable if necessary. To run the isadc information collector, the environs variable JAVA_HOME should exist set to the path of an installed java JRE. If the data collector tin not find a java JVM, it will prompt for the path to a JVM. On Windows, the following might be a skillful JAVA_HOME setting: On Linux or Unix, the following might be a practiced JAVA_HOME setting: |
| seven | Showtime the data collector either in the command prompt window or in a web browser. If you desire to run the data collector in a command prompt window without a GUI
Windows: .\isadc.bat Unix or Linux: ./isadc.sh You will be asked to have a software license agreement. And then, the same questions volition be asked in the non-GUI command prompt data collector every bit are asked when the data collector is running in the spider web browser (as described in the "Running the Data Collector in a Spider web Browser on an IBM FileNet Content Manager five.2.x Server Continued to the Net" section). If yous desire to run the data collector in a web browser directly from the downloaded and unzipped isadc binder
|
Source: https://www.ibm.com/support/pages/ibm-support-assistant-isa-data-collector-usge-ibm-filenet-content-platform-engine-52x
0 Response to "Why Does Isadc.sh Fail to Upload Files"
Postar um comentário