| 1. | Following is our entire basic content adapter code
下面是我们整个基本的内容适配器代码： |
| 2. | Write the content adapter code
编写内容适配器代码 |
| 3. | The following samples show content adapter code for both ins versions
下列的样本显示了两个ins版本的内容适配器代码。 |
| 4. | Device adapter code
设备适配器代码 |
| 5. | The steps for packaging and running a content adapter vary according to the type of content adapter
根据的类型不同，封装内容适配器代码和运行内容适配器的步骤也是变化的。 |
| 6. | Create and deploy adapter code referred to later as a message adapter that will run in a soap for cics environment
创建并部署将运行在用于cics的soap环境下的适配器代码（以下称为消息适配器） 。 |
| 7. | You want this in most cases because it simplifies the build and deployment of the adapter code to your target z os system
大多数情况下您需要这么做，因为它使构造和部署适配器代码到您的目标z / os系统更加简化。 |
| 8. | This adapter code becomes the message adapter to which soap for cics passes control when fulfilling a web service request for the existing cics cobol application
适配器代码成为消息适配器，当完成一个现有cics cobol应用程序的web服务请求后，用于cics的soap将传递控制给此消息适配器。 |
| 9. | The input converter , output converter , and the customized driver program together form the adapter code that interfaces with the existing cobol application and enables that cobol application with no modification to effectively consume and produce xml documents
输入转换器、输出转换器以及自定义的驱动程序一起组成了适配器代码，使之与现有的cobol应用程序连接，并且使cobol应用程序（没有做修改）能更有效的消费和生成xml文档。 |
| 10. | If your subscription requires that the content adapter run independently on the everyplace access server or on a remote server , you will need to package the content adapter code as an ear file and run it with the appserver launchclient application
如果您的订阅行为需要该内容适配器独立地运行在everyplace access服务器或者远程服务器上，您就必须将该内容适配器代码封装成ear文件，然后使用appserver launchclient应用程序运行该代码。 |
