在Install & Config 完 IBM FileNet之后，一個(gè)重要的事情就是check所安裝的AE，PE，CE是否安裝正確、能夠正常啟動(dòng)。 這里，簡(jiǎn)要列出一些check方法。
1. 啟動(dòng) CE DB .
與CE有關(guān)的一般有兩個(gè) DB。 一個(gè) 是 FNGCDDB用于記錄 CE Domain的一些配置信息。 主要有以FNGCD為 prefix 的四個(gè)表（FNGCD, FNGCD_ADDON, FNGCD_CESERVERS, FNGCD_OSCBROWNERS)。 當(dāng)你有需要想重新建立CE Domain的時(shí)候，最好將這四個(gè)表刪掉，然后重新建。
再一個(gè)DB就是 Object Store所在的DB，比如FNOS1DB. 在這個(gè)DB中，在建完Domain之后共有179張表。
值得注意的是，CE App Server是通過 DataSource來連接CE的DB的。所以，如果，有任何CE DB的改變，也同時(shí)需要更改DataSource。 顯而易見，因?yàn)橛袃蓚€(gè) CE DB，所以也有兩套CE DataSource， 一個(gè)是用于連接 FNGCDDB（還有個(gè)以XA結(jié)尾的，這個(gè)在運(yùn)行時(shí)經(jīng)常被用到），一個(gè)是用于連接FNOSDB，即Object Store DB。CE 就是靠這兩個(gè)Source來取得CE 信息的。
Check CE 狀態(tài)的方法：
http://localhost:9080/FileNet/Engine.
2. 啟動(dòng) AE。
由于 AE是一個(gè) WebApp 程序，所以只需要啟動(dòng) AE所在的 Server即可。
Check AE 狀態(tài)的方法：
http://localhost:9080/Workplace
3. 啟動(dòng) PE
PE 核心是一個(gè) C++程序。在運(yùn)行時(shí)， AE會(huì)嘗試連接 PE，CE，而PE和CE之間也有連接關(guān)系。
Windows based 的PE server需要注意有兩個(gè)系統(tǒng) Service（通過 Service.msc）是需要起來的。 一個(gè) 叫 PE Service Manager,一個(gè)是Img ControlService；需要檢查；
再有一個(gè) 重要的命令是 initfnsw,可以通過這個(gè)命令來起停 PE server。
① initfnsw start //-啟動(dòng)PE
② initfnsw stop //-停止PE
killfnsw -y //-停止PE
③ initfnsw status //-查看PE狀態(tài)
④ initfnsw restart //-重啟PE
另外， 檢查 PE的狀態(tài)，可以用這個(gè)URL 來 check，
http://localhost:32776/IOR/ping.
另外，有關(guān) PE 和 CE間連接性的檢查方法：
在 PE所在 Server上，用如下URL check，
http://localhost:32776/IOR/FileNet.CE.PEDirectoryServer
A "good" sample response from the PEDirectoryServer looks something like this:
IOR:000000000000002049444c3a46696c654e65745f63656d707270632f63656d707270633a312e300000000001000000000000007e000102000000000c31302e31352e372e31303800071d000000000031afabcb000000002084240cba00000001000000000000000100000008526f6f74504f41000000000800000001000000001400000000000002000000010000001800000000050100010000000000010109000000010001010000000026000000020002
此外，quick test are (on PE server):
If you’re having trouble with the PE to CE communications, there may be
something wrong with the java environment. Try the following tests in a
command prompt window on the PE Server (Substituting appropriate host
names, ports, user names, group names, and passwords as appropriate for
your configuration):
On your PE Server:
cd \fnsw\bin
Try a basic "little pipe" ping:
\fnsw\java\jre\bin\java -classpath pe.jar;pe3pt.jar filenet.pe.ceorb.test.PEDirectoryClientTest /port=32776 /rpc=ping
Set the little pipe’s CE connection configuration:
\fnsw\java\jre\bin\java -classpath pe.jar;pe3pt.jar
filenet.pe.ceorb.test.PEDirectoryClientTest /port=32776 /rpc=setConfig
/uri=http://hqbpm34:7001/wsi/FNCEWS40DIME/ /user=PEAdmin
/password=secret
Get a list of all realm names:
\fnsw\java\jre\bin\java -classpath pe.jar;pe3pt.jar filenet.pe.ceorb.test.PEDirectoryClientTest /port=32776 /rpc=getRealmNames
Get info about a user named PEAdmin:
\fnsw\java\jre\bin\java -classpath pe.jar;pe3pt.jar
filenet.pe.ceorb.test.PEDirectoryClientTest /port=32776 /rpc=getUserInfo
/user=PEAdmin
Get info about a user named PEAdmin in a specific realm:
\fnsw\java\jre\bin\java -classpath pe.jar;pe3pt.jar
filenet.pe.ceorb.test.PEDirectoryClientTest /port=32776 /rpc=getUserInfo
/user=PEAdmin /realm= dc=epbdc,dc=eng,dc=filenet,dc=com
Get info about a group named PEAdministrators:
\fnsw\java\jre\bin\java -classpath pe.jar;pe3pt.jar
filenet.pe.ceorb.test.PEDirectoryClientTest /port=32776 /rpc=getUserInfo
/user=PEAdministrators
Get “group expansion info” for a group named PEAdministrators:
\fnsw\java\jre\bin\java -classpath pe.jar;pe3pt.jar
filenet.pe.ceorb.test.PEDirectoryClientTest /port=32776 /rpc=expandGroup
/group=PEAdministrators
The above runs should produce output of some sort that might shed light on a CE configuration or connection problem…
取得 PE run 的 LOG：
Get some detailed information about the PE to CE communications
If the PE still can not get connected to the CE, we need to enable some
of the java tracing to see what’s happening when the PEDirectoryServer
communicates with the CE.
For PE 4.0.2 and newer, including PE 4.5
To enable the tracing, we need an fnlog4j.properties file in the
\fnsw\java\jre\lib directory on the PE Server. The fnlog4j.properties
file needs to include a line something like this:
log4j.logger.filenet.pe.ceorb.server=DEBUG, TXT
The easiest way to do this is to copy the
\fnsw_loc\sd\fnlog4j.properties.sample file as
\fnsw\jre\lib\fnlog4j.properties (without the “.sample”). Then, using a
simple text editor (e.g., notepad), add the “, TXT” to the above line
of text in the fnlog4j.properties file.
The PEDirectoryServer
will see the fnlog4j.properties file and that will trigger additional
tracing and logging to occur. After putting the fnlog4j.properties file
in the \fnsw\java\jre\lib directory, click the Apply button in the
Process Task Manager’s Security tab again.
After it fails,
check the java trace file. The location of the java trace file is
defined in the fnlog4j.properties file itself. By default, it's
c:\PE.txt.
3. 檢查 connection to PE from AE.
在登錄到 AE 之后，可以點(diǎn)擊 AE Site Preference中 Task Pages頁面，看是否能打開。以及PCC， Process Designer是否都能夠打開以及 Transfer Workflow.