3


来自集成组件的消息

Content Delivery Server 与外部组件(如订户数据库或 DRM 服务器)集成在一起。从这些组件或将这些组件与 Content Delivery Server 集成在一起的适配器接收的消息将写入 $CDS_HOME/deployment/deployment-name/conf 目录下的日志文件 CDS.log 中。

本章介绍了以下主题:


3.1 来自订户适配器的消息

Content Delivery Server 可通过订户适配器来使用包含订户信息的数据系统信息库。默认适配器在 Content Delivery Server 和 Oracle 数据库中存储的数据之间提供了一个接口。此外还提供了一个适配器,Content Delivery Server 可通过它来使用存储在基于轻量目录访问协议 (Lightweight Directory Access Protocol, LDAP) 格式的目录中的订户数据。

本节介绍了随 Content Delivery Server 提供的订户适配器所发出的消息。消息是通过消息号后跟类名及发出消息的方法名标识的。如果您使用自己的订户适配器,则可能会看到此处未介绍的其他消息。

3.1.1 来自 Oracle 适配器的消息

Oracle 数据库的订户适配器会将以下消息写入日志文件。所有消息均归类为严重级别。这些消息是按数字顺序组织的。

[cds.UserManager] SEVERE <0100> SubscriberImplDAO.createUser:A user already exists with either Unique Device Id = unique-device-ID or Mobile Id = mobile-ID or User Id = login-ID
[cds.UserManager] SEVERE <0101> SubscriberImplDAO.createUser:Failed to create user
[cds.UserManager] SEVERE <0104> SubscriberImplDAO.getUser:User ID cannot be NULL
[cds.UserManager] SEVERE <0106> SubscriberImplDAO.getUser:Failed to get user
[cds.UserManager] SEVERE <0107> SubscriberImplDAO.getUserByUniqueDeviceId:Failed to get CDSTransaction
[cds.UserManager] SEVERE <0108> SubscriberImplDAO.getUserByUniqueDeviceId:Failed to get user by unique device ID
[cds.UserManager] SEVERE <0110> SubscriberImplDAO.getUserByMobileId:Failed to get user by mobile ID
[cds.UserManager] SEVERE <0111> SubscriberImplDAO.updateUser:User cannot be NULL
[cds.UserManager] SEVERE <0112> SubscriberImplDAO.updateUser:A user already exists with either Unique Device Id = unique-device-ID or Mobile Id = mobile-ID or UserId = login-ID
[cds.UserManager] SEVERE <0113> SubscriberImplDAO.updateUser:Failed to update user

3.1.2 来自 LDAP 适配器的消息

LDAP 目录的订户适配器会将以下消息写入日志文件。所有消息均归类为严重级别。这些消息是按数字顺序组织的。

[cds.LDAPUserManager] SEVERE <0004> Cannot get mapping for loginId field
[cds.LDAPUserManager] SEVERE <0012> LDAPUserManager.doIsAuthenticated:Unexpected exception while checking authentication
[cds.LDAPUserManager] SEVERE <0016> LDAPUserManager.doUpdateUser:Cannot update user
[cds.LDAPUserManager] SEVERE <0032> LDAPUserManager.doAddUser:Cannot add user
[cds.LDAPUserManager] SEVERE <0035> LDAPUserManager.doDisableUser:Cannot disable user
[cds.LDAPUserManager] SEVERE <0037> LDAPUserManager.doRemoveUser:Cannot remove user
[cds.LDAPUserManager] SEVERE <0100> LDAPListHelper.createUser:Error in parsing config XML file
[cds.LDAPUserManager] SEVERE <0101> LDAPListHelper.createUser:Error in creating user


3.2 来自 DRM 处理的消息

为利用 Open Mobile Alliance (OMA) DRM 1.0 方法保护内容,Content Delivery Server 将使用您提供的有关 OMA DRM 1.0 指导的实现。在处理期间出现的错误将写入 Content Delivery Server 日志。

3.2.1 来自 DRM Fusion Toolkit 集成的消息

为了进行数字权限管理,Content Delivery Server 提供了 SafeNet DRM Fusion Toolkit 支持。DRM Fusion Toolkit 遇到的错误将写入 Content Delivery Server 日志。如果您使用 Open Mobile Alliance (OMA) DRM 1.0 指导的其他实现,则可能会看到此处未介绍的其他消息。

[cds.DRMFusion] SEVERE <0001> Failed to create usage profile usage-profile for edition id edition-ID
[cds.DRMFusion] SEVERE <0003> Could not get rights for content-ID
[cds.DRMFusion] SEVERE <0004> Failed to initialize the integration with DRM Fusion Toolkit, please check the setup environment.
[cds.DRMFusion] SEVERE <0007> Failed to protect content id content-ID
[cds.DRMFusion] SEVERE <0008> Failed to store plain file at file-location 
[cds.DRMFusion SEVERE] <0009> Failed to read protected file file
[cds.DRMFusion] SEVERE <0010> Failed to create rights.OMA Technology :delivery-mechanism and pricemodel id :pricemodel-db-pk 

3.2.2 OMA 消息

无法传送数字权限对象时将发出以下消息

[cds.OMA] SEVERE <0001> Failed to send rights for content id content-ID to phone number phone-number


3.3 来自推送发送器或推送监听器适配器的消息

以下消息是由消息传送 API 的实现(推送发送器适配器或推送监听器适配器)发出的。这些消息是按数字顺序组织的。

[cds.MsgServer] SEVERE <0034> Error while sending SMS Push message using CIMD2
[cds.MsgServer] SEVERE <0040> Connection could not be established java.net.UnknownHostException
[cds.MsgServer] SEVERE <0126> FAILED TO CONNECT TO SMSC 
[cds.MsgServer] INFO <0127> Will try to reconnect after 60000 milliseconds
[cds.MsgServer] SEVERE <0054> Error while sending message to WAP PPG com.sun.content.server.messagingservice.msgserver.protocolPpgConnectionFailedException:Failed to connect to wap ppg server
[cds.MsgServer] SEVERE <0070> Error while sending SMS Push message using SMPP
[cds.MsgServer] SEVERE <0130> CONNECTION BROKEN
[cds.MsgServer] SEVERE <0184> Invalid SMSC host name specified in the properties file 
[cds.MsgServer] SEVERE <0185> Invalid SMSC port number specified in the properties file
[cds.MsgServer] SEVERE <0194> Error while sending SMS Push message using HTTP