Installing enterprise application files

As part of deploying an application, you install application files on a server configured to hold installable modules.

Before you begin

Before you can install your Java™ Platform, Enterprise Edition (Java EE) application files on an application server, you must assemble modules as needed.

Also, before you install the files, configure the target application server. As part of configuring the server, determine whether your application files can be installed to your deployment targets.

支援的配置 支援的配置: Installation of new Java EE specification levels are not allowed on deployment targets that do not support the specified Java EE level. For example, if an application contains modules with an EJB deployment descriptor level of 3.1 (part of Java EE 6), the application cannot be installed on an application server that does not support Java EE 6, such as application server versions prior to Version 8. Further, if an application contains Java EE 6 annotations, the application cannot be installed on an application server that does not support the Java EE 6 specification level, even if the application contains an EJB deployment descriptor for a previous version of the supported Java EE specification level; for example, EJB 3.0 which is part of Java EE 5.sptcfg

About this task

You can install the following enterprise modules on a server:

  • Enterprise archive (EAR)
  • Enterprise bean (EJB)
  • Web archive (WAR)
  • Session Initiation Protocol (SIP) module (SAR)
  • Resource adapter (connector or RAR)
  • Application client modules

Application client files can be installed in a WebSphere® Application Server configuration but cannot be run on a server.

Complete the following steps to install your files.

Procedure

  1. Determine which method to use to install your application files. The product provides several ways to install modules.
  2. Install the application files using
    • Administrative console
    • [AIX Solaris HP-UX Linux Windows][z/OS]Drag and drop to a monitored directory
    • wsadmin scripts
    • Java administrative programs that use Java Management Extensions (JMX) application programming interfaces (APIs)
  3. Start the deployed application files using
    • Administrative console
    • wsadmin startApplication
    • Java programs that use ApplicationManager or AppManagement MBeans

What to do next

Save the changes to your administrative configuration.

When saving the configuration in multiple-server environments, synchronize the configuration with the nodes where the application is expected to run.

避免困難 避免困難:
  • 您必須使用管理主控台或 wsadmin Scripting 來同步化節點。在這兩個選項中,使用管理主控台是執行這項作業的最佳方法。管理主控台中的「節點」畫面包括同步化作業。

    如果您需要使用 wsadmin Scripting 來同步化節點,請使用 NodeSync MBean 的 sync() 指令。

  • 在同步化節點過程中,請勿重新啟動節點代理程式。透過節點代理程式起始並會影響應用程式伺服器的管理作業(例如,用於應用程式部署的節點同步化,或節點代理程式啟動時進行的更新),在節點代理程式有機會探索應用程式伺服器之前會失敗。
gotcha
Important: After any change to application deployment or mapping, it is always best to generate and propagate the plugin-cfg.xml. For your production environment, make sure the generated plugin-cfg.xml is correct because the propagation of the plugin to the target web server will cause the plugin configuration properties to be reloaded.

Next, test the application. For example, point a web browser at the URL for a deployed application. Typically, the URL is http://hostname:9060/web_module_name, where hostname is your valid web server and 9060 is the default port number. Examine the performance of the application. If the application does not perform as desired, edit the application configuration, then save and test it again.

If your application contains many classes with annotations and takes a long time to deploy, you can reduce annotation searches to speed up deployment. See the topic on reducing annotation searches during application deployment.


指出主題類型的圖示 作業主題



時間戳記圖示 前次更新: July 9, 2016 11:16
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=trun_app_install
檔名:trun_app_install.html