安装分析后，我的Worklight 6.2控制台上没有运行时

Question

我刚刚安装了Worklight 6.2服务器，使用配置工具部署一个简单的项目，它可以正常工作。然后，我按照知识中心的指示安装了分析软件。之后，当我在浏览器中打开WL控制台时，我得到了“无法找到运行时”。分析似乎很好

我的war文件在自由应用程序文件夹中。在我的例子中，C:\IBM\WebSphere\Liberty\usr\servers\simpleServer\apps

我已经尝试了下面的解决方案，但没有奏效。我删除了工作区中的文件，并检查了jdk，即jdk6_45 No runtime on my Worklight 6.2 Console。

这是我的server.xml

​

<!-- Enable features -->
<featureManager>
    <feature>jsp-2.2</feature>

    <!-- Begin for analytics -->
    <feature>jsp-2.2</feature>
    <feature>jndi-1.0</feature>
    <!-- End for analytics -->

    <!-- Begin of features added by IBM Worklight installer. -->
    <feature>ssl-1.0</feature>
    <feature>servlet-3.0</feature>
    <feature>jdbc-4.0</feature>
    <feature>appSecurity-1.0</feature>
    <feature>jndi-1.0</feature>
    <!-- End of features added by IBM Worklight installer. -->


    <!-- Begin of features added by IBM Worklight <installWorklightAdmin> ant task for context root '/wladmin'. -->
    <feature>ssl-1.0</feature>
    <feature>servlet-3.0</feature>
    <feature>jdbc-4.0</feature>
    <feature>jndi-1.0</feature>
    <!-- <feature>restConnector-1.0</feature> -->
    <feature>appSecurity-1.0</feature>
    <!-- End of features added by IBM Worklight <installWorklightAdmin> ant task for context root '/wladmin'. -->


    <!-- Begin of features added by IBM Worklight <configureApplicationServer> ant task for context root '/worklight'. -->
    <feature>ssl-1.0</feature>
    <feature>servlet-3.0</feature>
    <feature>jdbc-4.0</feature>
    <feature>jndi-1.0</feature>
    <!-- End of features added by IBM Worklight <configureApplicationServer> ant task for context root '/worklight'. -->

</featureManager>

<httpEndpoint id="defaultHttpEndpoint"
              host="*"
              httpPort="9080"
              httpsPort="9443" >

    <!-- Option soReuseAddr added by IBM Worklight installer. -->
    <!-- Option soReuseAddr added by IBM Worklight <installWorklightAdmin> ant task for context root '/wladmin'. -->
    <!-- Option soReuseAddr added by IBM Worklight <configureApplicationServer> ant task for context root '/worklight'. -->
    <tcpOptions soReuseAddr="true"/>

</httpEndpoint>

<!-- Begin of configuration added by IBM Worklight installer. -->

<!-- Declare the IBM Application Center Console application. -->
<application id="appcenterconsole" name="appcenterconsole" location="appcenterconsole.war" type="war">
    <application-bnd>
        <security-role name="appcenteradmin">
            <group name="appcentergroup"/>
        </security-role>
    </application-bnd>
</application>

<!-- Declare the IBM Application Center Services application. -->
<application id="applicationcenter" name="applicationcenter" location="applicationcenter.war" type="war">
    <application-bnd>
        <security-role name="appcenteradmin">
            <group name="appcentergroup"/>
        </security-role>
    </application-bnd>
    <classloader delegation="parentLast">
        <commonLibrary>
            <fileset dir="${wlp.install.dir}/lib" includes="com.ibm.ws.crypto.passwordutil_1.0.1.jar"/>
        </commonLibrary>
    </classloader>
</application>

<!-- Declare the user registry for the IBM Application Center. -->
<basicRegistry id="applicationcenter-registry" realm="ApplicationCenter">
    <!--    Worklight user.
    [Added by IBM Worklight <installWorklightAdmin> Ant task for context root '/wladmin'] 
    -->
    <user name="WorklightRESTUser" password="WGFtAaW8fTma"/>

    <!-- The users defined here are members of group "appcentergroup",
         thus have role "appcenteradmin", and can therefore perform
         administrative tasks through the IBM Application Center Console. -->
    <user name="appcenteradmin" password="admin"/>

    <user name="demo" password="demo"/>
    <group name="appcentergroup">
        <member name="appcenteradmin"/>
        <member name="demo"/>
    </group>
</basicRegistry>

<!-- Declare the JNDI properties for the IBM Application Center. -->

<!-- Define the AppCenter services endpoint in order for the AppCenter console to be able to invoke the REST service.
        You need to enable this property if the server is behind a reverse proxy
        or if the context root of the Application Center Services application is different from '/applicationcenter'. -->
<!-- <jndiEntry jndiName="ibm.appcenter.services.endpoint" value='"http://proxyhost:proxyport/applicationcenter"'/> -->
<!-- The directory with binaries of the 'aapt' program, from the Android SDK's platform-tools package. -->
<jndiEntry jndiName="android.aapt.dir" value='"C:/IBM/Worklight/ApplicationCenter/tools/android-sdk"'/>
<!-- The protocol of the application resources URI. This property is optional. It is only needed if the protocol of the external and internal URI are different. -->
<!-- <jndiEntry jndiName="ibm.appcenter.proxy.protocol" value='"http"'/> -->
<!-- The hostname of the application resources URI. -->
<!-- <jndiEntry jndiName="ibm.appcenter.proxy.host" value='"proxyhost"'/> -->
<!-- The port of the application resources URI. This property is optional. -->
<!-- <jndiEntry jndiName="ibm.appcenter.proxy.port" value="proxyport"/> -->

<!-- Declare the jar files for DB2 access through JDBC. -->
<library id="DB2Lib">
    <fileset dir="${shared.resource.dir}/db2" includes="*.jar"/>
</library>

<!-- Declare the IBM Application Center database. -->
<dataSource jndiName="jdbc/AppCenterDS" transactional="false">
    <jdbcDriver libraryRef="DB2Lib"/>
    <properties.db2.jcc databaseName="APPCNTR" serverName="localhost" portNumber="50000" user="db2admin" password="db2admin"/>
</dataSource>

<!-- End of configuration added by IBM Worklight installer. -->

上下文根‘/wladmin’的Ant任务]此配置是创建SSL配置所需的最小配置。使用此配置，自由服务器将在SSL初始化期间创建密钥存储库和证书(如果还不存在)。创建的证书是一个自签名证书，有效期为365天.不要使用自由服务器为生产使用而创建的证书。有关更多信息，请参见ssl.html -->

<administrator-role>
    <!--    Worklight JMX User.
    [Added by IBM Worklight <installWorklightAdmin> Ant task for context root '/wladmin'] 
    -->
    <user>WorklightRESTUser</user>

</administrator-role>
<!--    Worklight JNDI property for JMX connection.
    [Added by IBM Worklight <installWorklightAdmin> Ant task for context root '/wladmin'] 
-->
<jndiEntry jndiName="ibm.worklight.admin.jmx.host" value="localhost"/>
<!--    Worklight JNDI property for JMX connection.
    [Added by IBM Worklight <installWorklightAdmin> Ant task for context root '/wladmin'] 
-->
<jndiEntry jndiName="ibm.worklight.admin.jmx.port" value="9443"/>
<!--    Worklight JNDI property for JMX connection.
    [Added by IBM Worklight <installWorklightAdmin> Ant task for context root '/wladmin'] 
-->
<jndiEntry jndiName="ibm.worklight.admin.jmx.user" value="WorklightRESTUser"/>
<!--    Worklight JNDI property for JMX connection.
    [Added by IBM Worklight <installWorklightAdmin> Ant task for context root '/wladmin'] 
-->
<jndiEntry jndiName="ibm.worklight.admin.jmx.pwd" value="WGFtAaW8fTma"/>
<!--    Worklight JNDI property for JMX connection.
    [Added by IBM Worklight <installWorklightAdmin> Ant task for context root '/wladmin'] 
-->
<jndiEntry jndiName="ibm.worklight.topology.platform" value="Liberty"/>
<!--    Worklight JNDI property for JMX connection.
    [Added by IBM Worklight <installWorklightAdmin> Ant task for context root '/wladmin'] 
-->
<jndiEntry jndiName="ibm.worklight.topology.clustermode" value="Standalone"/>

<!-- Begin of configuration added by IBM Worklight <installWorklightAdmin> ant task for context root '/wladmin'. -->

<!-- Declare the Worklight Administration Service application. -->
<application id="wladmin" name="wladmin" location="worklightadmin.war" type="war">
    <application-bnd>
        <security-role name="worklightadmin">
            <user name="demo"/>

        </security-role>

        <security-role name="worklightdeployer">
        </security-role>

        <security-role name="worklightmonitor">
        </security-role>

        <security-role name="worklightoperator">
        </security-role>

    </application-bnd>

    <classloader delegation="parentLast">
        <commonLibrary>

            <fileset dir="${wlp.install.dir}/lib" includes="com.ibm.ws.crypto.passwordutil_1.0.1.jar"/>
        </commonLibrary>
    </classloader>
</application>

<!-- Declare web container custom properties for the Worklight Administration Service application. -->
<webContainer invokeFlushAfterService="false" deferServletLoad="false"/>

<!-- Declare the JNDI properties for the Worklight Administration Service. -->
<jndiEntry jndiName="wladmin/ibm.worklight.admin.environmentid" value='"Hello_Worklight_Server"'/>


<!-- Declare the jar files for DB2 access through JDBC. -->
<library id="wladmin/DB2Lib">
    <fileset dir="${shared.resource.dir}/wladmin/db2" includes="db2jcc4.jar,db2jcc_license_cu.jar"/>
</library>

<!-- Declare the IBM Worklight Administration database. -->
<dataSource jndiName="wladmin/jdbc/WorklightAdminDS" transactional="false">
    <jdbcDriver libraryRef="wladmin/DB2Lib"/>
    <properties.db2.jcc databaseName="WRKLGHT" serverName="localhost" portNumber="50000" user="db2admin" password="db2admin" currentSchema="WLADMIN"/>
</dataSource>

<!-- Declare the Worklight Administration Console application. -->
<application id="worklightconsole" name="worklightconsole" location="worklightconsole.war" type="war">
    <application-bnd>
        <security-role name="worklightadmin">
            <user name="demo"/>

        </security-role>

        <security-role name="worklightdeployer">
        </security-role>

        <security-role name="worklightmonitor">
        </security-role>

        <security-role name="worklightoperator">
        </security-role>

    </application-bnd>

</application>

<!-- Declare web container custom properties for the Worklight Administration Console application. -->
<webContainer invokeFlushAfterService="false" deferServletLoad="false"/>

<!-- Declare the JNDI properties for the Worklight Administration Console. -->
<jndiEntry jndiName="worklightconsole/ibm.worklight.admin.endpoint" value='"*://*:*/wladmin"'/>


<!-- End of configuration added by IBM Worklight <installWorklightAdmin> ant task for context root '/wladmin'. -->


<!-- Begin of configuration added by IBM Worklight <configureApplicationServer> ant task for context root '/worklight'. -->

<!-- Declare the IBM Worklight project runtime application. -->
<application id="worklight" name="worklight" location="HelloWorklight.war" type="war">
    <classloader delegation="parentLast">
        <privateLibrary>
            <fileset dir="${shared.resource.dir}/worklight/lib" includes="worklight-jee-library.jar"/>
        </privateLibrary>
    </classloader>
</application>

<!-- Declare the JNDI properties for the IBM Worklight project runtime. -->
<jndiEntry jndiName="worklight/publicWorkLightProtocol" value='"http"'/>
<jndiEntry jndiName="worklight/publicWorkLightPort" value='"9080"'/>
<jndiEntry jndiName="worklight/ibm.worklight.admin.environmentid" value='"Hello_Worklight_Server"'/>


<!-- Declare the jar files for DB2 access through JDBC. -->
<library id="worklight/DB2Lib">
    <fileset dir="${shared.resource.dir}/worklight/db2" includes="db2jcc4.jar,db2jcc_license_cu.jar"/>
</library>

<!-- Declare the IBM Worklight Server database. -->
<dataSource jndiName="worklight/jdbc/WorklightDS" transactional="false">
    <jdbcDriver libraryRef="worklight/DB2Lib"/>
    <properties.db2.jcc databaseName="WRKLGHT" serverName="localhost" portNumber="50000" user="db2admin" password="db2admin" currentSchema="WRKLGHT"/>
</dataSource>

<!-- Declare the IBM Worklight Server reports database. -->
<dataSource jndiName="worklight/jdbc/WorklightReportsDS" transactional="false">
    <jdbcDriver libraryRef="worklight/DB2Lib"/>
    <properties.db2.jcc databaseName="WRKLGHT" serverName="localhost" portNumber="50000" user="db2admin" password="db2admin" currentSchema="WLREPORT"/>
</dataSource>

<!-- For analytics -->
<application context-root="/analytics"
     id="analytics"
     location="analytics.war"
     name="analytics"
     type="war">
</application>

<!-- End of configuration added by IBM Worklight <configureApplicationServer> ant task for context root '/worklight'. -->

​

Answer 1

Worklight仍然需要自由中的restConnector-1.0特性，所以您不应该将它注释掉。当restConnector特性出现时，6.2中提供的分析无法运行。你有两个选择：

选项1 -下载最新的iFix。最新的iFix附带了一个可以与restConnector特性一起运行的分析版本。您必须将“parentLast”类加载器声明添加到server.xml中的分析项中。示例：

<应用程序上下文-根=“/analytics”id=分析“location=”analytics.war“name=”分析“type=”war>

选项2 -将分析安装在单独的自由服务器上(推荐用于生产服务器的方法)

上述文件将在下一个补丁中更新。

顺便提一句，您确定“无运行时”错误与分析有关，而不仅仅是巧合吗？当您删除分析并反转安装步骤时，是否仍然会发生错误？