EAS instance starts reported the existence of illegal assembly systems, instances failed to start:
Assembly inspection mechanism, in addition to the requirements
$EAS_HOME eas\server\lib；
$EAS_HOME \eas\server\deploy\fileserver.ear\easWebClient\lib；
$EAS_HOME eas\server\metas；
$EAS_HOME\eas\server\deploy\fileserver.ear\easWebClient\metas；
And an outer sp bim four directories under the directory, the directory does not allow other people to modify or storage jar package; but in some special cases, after site assessment, does need to modify or confirm storage jar, placed in the need to modify or after the jar, regenerated reference unit. :
Solution:
EAS750 version regenerate the baseline file method:
Step 1 Delete $ EAS_HOME \ eas \ server \ properties \ componentsbase.xml file.
Step 2. Modify $ EAS_HOME \ eas \ admin \ config \ domain.xml file deployed = "true" is deployed = "false"
To run the 3 eas \ stopserver.cmd (stopserver.sh) admin directory, then run admin.cmd (admin.sh) Restart Manager console, regenerate the reference file and follow the prompts to re-deploy instance,
It will re-generate the reference file.
EAS800 version regenerate the baseline file method:
Step 1 modified file $ EAS_HOME /eas/admin/config/record.properties, wherein the modified parameter isAlreadyGenerateComponentBase = true isAlreadyGenerateComponentBase = false.
Step 2 application server tab point EAS management console "Refresh" button to regenerate the reference files.
A few remarks about the routing address changes:
D:\kingdee\kdserver\eas\server\profiles\server1\config\portalConfig/ssoClient
F:\easServerV82\server\eas\admin\config 新增isDetectIllegalComponents=false