埋め込みTomcatでSpringブートを使用してEJBトランスポート経由でWebsphere 8.5上で動作するFilenetに接続

Question

EJBトランスポートを使用するFilenet CEAPIを使用してSpringブートアプリケーションを開発しています（Filenet Web Service（CEWS）接続はオプションではありません）。私は私が上で、次のエラーを取得し、何度も何度毎秒で、私の春ブーツアプリを実行しよう：

NMSV0307E：Javaの：URL名を使用したが、ネーミングは ハンドルのjavaに構成されていなかった：URL名。考えられる原因は、エラーのあるユーザが、 を使用して、非J2EEクライアントまたはサーバのjava：URL名を指定することです。 環境。 ConfigurationExceptionをスローします。

私の設定は次のとおりです。

spring.version = 4.2.2.RELEASE 

spring.boot.version = 1.2.7.RELEASE 
       (I’ve tried 1.4.0.RELEASE, but I got the same results) 

Websphere = 8.5 - this runs the Filenet Content Engine 

Filenet & CEAPI = 5.2.1 - using EJB connection 

私はチュートリアル使用しました：私はこのStackOverflowのエントリを使用してTomcatのJNDIネーミングを有効にしているhttp://www.notonlyanecmplace.com/how-to-connect-via-ejb-to-p8-5-2-and-websphere-v8-5/

を：

How to create JNDI context in Spring Boot with Embedded Tomcat Container

が、 tomcat.enableNaming();行にブレークポイントを追加すると私はJNDI経由で何を検索したくないので、FileNetのAPIがあることないので、私は、残りの部分を使用していない

@Bean 
public TomcatEmbeddedServletContainerFactory tomcatFactory() { 
    return new TomcatEmbeddedServletContainerFactory() { 

     @Override 
     protected TomcatEmbeddedServletContainer getTomcatEmbeddedServletContainer(
       Tomcat tomcat) { 
      tomcat.enableNaming(); 
      return super.getTomcatEmbeddedServletContainer(tomcat); 
     } 
    }; 
} 

：...私は、このソリューションのこの部分を使用してい

を停止。

要約：誰かが、Spring Boot 1.2.7とEmbedded Tomcatを使用して、Filenet Java APIを使用してEJB転送プロトコルでWebsphere 8.5アプリケーションサーバー上で動作するFilenetに接続する方法を教えてください。

EDIT：

のFileNet APIは、WebSphereサーバーからoptained以下のファイルを使用しています：

com.ibm.ws.orb_8.5.0.jar 
com.ibm.ws.ejb.thinclient_8.5.0 
key.p12 
sas.client.props 
ssl.client.props 
trust.p12 

EDIT＃2：

私はログメッセージの新しいセットを持っていますロギングの精製後：

2016-09-02 10:45:37.581 DEBUG 8820 --- [P=678944:O=0:CT] o.s.c.e.PropertySourcesPropertyResolver : Searching for key 'context.listener.classes' in [servletConfigInitParams] 
2016-09-02 10:45:37.597 DEBUG 8820 --- [P=678944:O=0:CT] o.s.c.e.PropertySourcesPropertyResolver : Searching for key 'context.listener.classes' in [servletContextInitParams] 
2016-09-02 10:45:37.597 DEBUG 8820 --- [P=678944:O=0:CT] o.s.c.e.PropertySourcesPropertyResolver : Searching for key 'context.listener.classes' in [jndiProperties] 
2016-09-02 10:45:37.597 DEBUG 8820 --- [P=678944:O=0:CT] org.springframework.jndi.JndiTemplate : Looking up JNDI object with name [java:comp/env/context.listener.classes] 
2016-09-02 10:45:37.598 ERROR 8820 --- [P=678944:O=0:CT] c.i.w.naming.java.javaURLContextFactory : javaAccessorNotSet 
2016-09-02 10:45:37.598 DEBUG 8820 --- [P=678944:O=0:CT] o.s.jndi.JndiLocatorDelegate    : Converted JNDI name [java:comp/env/context.listener.classes] not found - trying original name [context.listener.classes]. javax.naming.ConfigurationException: Name space accessor for the java: name space has not been set. Possible cause is that the user is specifying a java: URL name in a JNDI Context method call but is not running in a J2EE client or server environment. 
2016-09-02 10:45:37.599 DEBUG 8820 --- [P=678944:O=0:CT] org.springframework.jndi.JndiTemplate : Looking up JNDI object with name [context.listener.classes] 
2016-09-02 10:45:38.623 DEBUG 8820 --- [P=678944:O=0:CT] o.s.jndi.JndiPropertySource    : JNDI lookup for name [context.listener.classes] threw NamingException with message: Could not obtain an initial context due to a communication failure. Since no provider URL was specified, the default provider URL of "corbaloc:iiop:1.0@<MY_COMPUTERS_ADDRESS>:2809/NameService" was used. Make sure that any bootstrap address information in the URL is correct and that the target name server is running. Possible causes other than an incorrect bootstrap address or unavailable name server include the network environment and workstation network configuration.. Returning null. 
2016-09-02 10:45:38.623 DEBUG 8820 --- [P=678944:O=0:CT] o.s.c.e.PropertySourcesPropertyResolver : Searching for key 'context.listener.classes' in [systemProperties] 
2016-09-02 10:45:38.623 DEBUG 8820 --- [P=678944:O=0:CT] o.s.c.e.PropertySourcesPropertyResolver : Searching for key 'context.listener.classes' in [systemEnvironment] 
2016-09-02 10:45:38.624 DEBUG 8820 --- [P=678944:O=0:CT] o.s.c.e.PropertySourcesPropertyResolver : Searching for key 'context.listener.classes' in [random] 
2016-09-02 10:45:38.624 DEBUG 8820 --- [P=678944:O=0:CT] o.s.c.e.PropertySourcesPropertyResolver : Searching for key 'context.listener.classes' in [applicationConfigurationProperties] 
2016-09-02 10:45:38.624 DEBUG 8820 --- [P=678944:O=0:CT] o.s.c.e.PropertySourcesPropertyResolver : Could not find key 'context.listener.classes' in any property source. Returning [null] 
2016-09-02 10:45:38.625 DEBUG 8820 --- [P=678944:O=0:CT] org.springframework.jndi.JndiTemplate : Looking up JNDI object with name [java:comp/env/spring.mandatoryFileEncoding] 
2016-09-02 10:45:38.627 ERROR 8820 --- [P=678944:O=0:CT] c.i.w.naming.java.javaURLContextFactory : javaAccessorNotSet 
2016-09-02 10:45:38.627 DEBUG 8820 --- [P=678944:O=0:CT] o.s.jndi.JndiLocatorDelegate    : Converted JNDI name [java:comp/env/spring.mandatoryFileEncoding] not found - trying original name [spring.mandatoryFileEncoding]. javax.naming.ConfigurationException: Name space accessor for the java: name space has not been set. Possible cause is that the user is specifying a java: URL name in a JNDI Context method call but is not running in a J2EE client or server environment. 
2016-09-02 10:45:38.627 DEBUG 8820 --- [P=678944:O=0:CT] org.springframework.jndi.JndiTemplate : Looking up JNDI object with name [spring.mandatoryFileEncoding] 
2016-09-02 10:45:39.634 DEBUG 8820 --- [P=678944:O=0:CT] o.s.jndi.JndiPropertySource    : JNDI lookup for name [spring.mandatoryFileEncoding] threw NamingException with message: Could not obtain an initial context due to a communication failure. Since no provider URL was specified, the default provider URL of "corbaloc:iiop:1.0@<MY_COMPUTERS_ADDRESS>:2809/NameService" was used. Make sure that any bootstrap address information in the URL is correct and that the target name server is running. Possible causes other than an incorrect bootstrap address or unavailable name server include the network environment and workstation network configuration.. Returning null. 
2016-09-02 10:45:39.635 DEBUG 8820 --- [P=678944:O=0:CT] org.springframework.jndi.JndiTemplate : Looking up JNDI object with name [java:comp/env/spring.mandatory_file_encoding] 
2016-09-02 10:45:39.636 ERROR 8820 --- [P=678944:O=0:CT] c.i.w.naming.java.javaURLContextFactory : javaAccessorNotSet 
2016-09-02 10:45:39.636 DEBUG 8820 --- [P=678944:O=0:CT] o.s.jndi.JndiLocatorDelegate    : Converted JNDI name [java:comp/env/spring.mandatory_file_encoding] not found - trying original name [spring.mandatory_file_encoding]. javax.naming.ConfigurationException: Name space accessor for the java: name space has not been set. Possible cause is that the user is specifying a java: URL name in a JNDI Context method call but is not running in a J2EE client or server environment. 
2016-09-02 10:45:39.637 DEBUG 8820 --- [P=678944:O=0:CT] org.springframework.jndi.JndiTemplate : Looking up JNDI object with name [spring.mandatory_file_encoding] 
2016-09-02 10:45:40.645 DEBUG 8820 --- [P=678944:O=0:CT] o.s.jndi.JndiPropertySource    : JNDI lookup for name [spring.mandatory_file_encoding] threw NamingException with message: Could not obtain an initial context due to a communication failure. Since no provider URL was specified, the default provider URL of "corbaloc:iiop:1.0@<MY_COMPUTERS_ADDRESS>:2809/NameService" was used. Make sure that any bootstrap address information in the URL is correct and that the target name server is running. Possible causes other than an incorrect bootstrap address or unavailable name server include the network environment and workstation network configuration.. Returning null. 
2016-09-02 10:45:40.646 DEBUG 8820 --- [P=678944:O=0:CT] org.springframework.jndi.JndiTemplate : Looking up JNDI object with name [java:comp/env/spring.mandatory-file-encoding] 
2016-09-02 10:45:40.646 ERROR 8820 --- [P=678944:O=0:CT] c.i.w.naming.java.javaURLContextFactory : javaAccessorNotSet 

Answer 1

NMSV0307E WebSphereエラーでは、java:名前空間を管理対象環境（アプリケーションサーバーまたはアプリケーションクライアント）の外部に使用することはできません。たとえば、EJBを含むWebSphere Application ServerのSystemOut.log内の関連するCNTR0167Iメッセージを探して、その名前をルックアップに使用するなど、EJBの実際のバインディング名を見つける必要があります。