当前位置: 技术问答>java相关
在本地测试通过的EJB,如何把测试程序放在另外一台机器上,也可以测试通过。
来源: 互联网 发布时间:2015-07-13
本文导语: 测试通过的机器:win2000+weblogic6.1 需要把测试程序(CLIENT端的程序)放在另外一台机器的上的配置:WIN2000+JRE2.0 EJB程序和测试程序都是在JBUILDER中生成的。 | 这个基本上实现不了,为什么叫测试...
测试通过的机器:win2000+weblogic6.1
需要把测试程序(CLIENT端的程序)放在另外一台机器的上的配置:WIN2000+JRE2.0
EJB程序和测试程序都是在JBUILDER中生成的。
需要把测试程序(CLIENT端的程序)放在另外一台机器的上的配置:WIN2000+JRE2.0
EJB程序和测试程序都是在JBUILDER中生成的。
|
这个基本上实现不了,为什么叫测试客户端呢,是用做你测试时用的,而不是你应用的一部分,拿到那里都可以,因为ejb设计到命名服务,目录服务,这些你要在命令行都实现了后,那你的测试客护短才可以放在任何地方
|
也就是:
(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
properties.put(Context.PROVIDER_URL, url);
if (user != null) {
properties.put(Context.SECURITY_PRINCIPAL, "System"
properties.put(Context.SECURITY_CREDENTIALS, "12345678");
}
(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
properties.put(Context.PROVIDER_URL, url);
if (user != null) {
properties.put(Context.SECURITY_PRINCIPAL, "System"
properties.put(Context.SECURITY_CREDENTIALS, "12345678");
}
|
能ping 通192.168.1.125么??
|
t3://192.168.1.125:7001这机的user=? password=?
你能确定他们吗?
你能确定他们吗?
|
weblogic安装后默认无需设置用户和密码就能访问,但只能访问不能deploy
|
给一个e文你看看:
Application Client-Tier Security
Authentication requirements for J2EE application clients are the same as the requirements for other J2EE components. Access to protected resources in either the EJB tier or the Web tier requires user authentication, whereas access to unprotected resources does not.
An application client can use the Java Authentication and Authorization Service (JAAS) for authentication. JAAS implements a Java version of the standard Pluggable Authentication Module (PAM) framework, which permits applications to remain independent from underlying authentication technologies. You can plug new or updated authentication technologies under an application without making any modifications to the application itself. Applications enable the authentication process by instantiating a LoginContext object, which, in turn, references a configuration to determine the authentication technologies or login modules that will be used to perform the authentication.
A typical login module could prompt for and verify a user name and password. Other modules could read and verify a voice or fingerprint sample.
In some cases, a login module needs to communicate with the user to obtain authentication information. Login modules use a javax.security.auth.callback.CallbackHandler for this purpose. Applications implement the CallbackHandler interface and pass it to the login context, which forwards it directly to the underlying login modules. A login module uses the callback handler both to gather input (such as a password or smart card PIN number) from users or to supply information (such as status information) to users. By allowing the application to specify the callback handler, an underlying login module can remain independent of the different ways applications interact with users.
For example, the implementation of a callback handler for a GUI application might display a window to solicit user input. Or, the implementation of a callback handler for a command line tool might simply prompt the user for input directly from the command line.
The login module passes an array of appropriate callbacks to the callback handler's handle method (for example, a NameCallback for the user name and a PasswordCallback for the password), and the callback handler performs the requested user interaction and sets appropriate values in the callbacks. For example, to process a NameCallback, the CallbackHandler may prompt for a name, retrieve the value from the user, and call the setName method of the NameCallback to store the name.
更详细的请从:http://java.sun.com/j2ee/download.html#tutorial下载。
Application Client-Tier Security
Authentication requirements for J2EE application clients are the same as the requirements for other J2EE components. Access to protected resources in either the EJB tier or the Web tier requires user authentication, whereas access to unprotected resources does not.
An application client can use the Java Authentication and Authorization Service (JAAS) for authentication. JAAS implements a Java version of the standard Pluggable Authentication Module (PAM) framework, which permits applications to remain independent from underlying authentication technologies. You can plug new or updated authentication technologies under an application without making any modifications to the application itself. Applications enable the authentication process by instantiating a LoginContext object, which, in turn, references a configuration to determine the authentication technologies or login modules that will be used to perform the authentication.
A typical login module could prompt for and verify a user name and password. Other modules could read and verify a voice or fingerprint sample.
In some cases, a login module needs to communicate with the user to obtain authentication information. Login modules use a javax.security.auth.callback.CallbackHandler for this purpose. Applications implement the CallbackHandler interface and pass it to the login context, which forwards it directly to the underlying login modules. A login module uses the callback handler both to gather input (such as a password or smart card PIN number) from users or to supply information (such as status information) to users. By allowing the application to specify the callback handler, an underlying login module can remain independent of the different ways applications interact with users.
For example, the implementation of a callback handler for a GUI application might display a window to solicit user input. Or, the implementation of a callback handler for a command line tool might simply prompt the user for input directly from the command line.
The login module passes an array of appropriate callbacks to the callback handler's handle method (for example, a NameCallback for the user name and a PasswordCallback for the password), and the callback handler performs the requested user interaction and sets appropriate values in the callbacks. For example, to process a NameCallback, the CallbackHandler may prompt for a name, retrieve the value from the user, and call the setName method of the NameCallback to store the name.
更详细的请从:http://java.sun.com/j2ee/download.html#tutorial下载。