星期二, 三月 20, 2007

JBOSS上部署JOSSO单点登录组件

本文主要阐述在编译,打包和在JBOSS上部署和运行JOSSO单点登陆程序的步骤,认证数据存放Mysql数据库

####################################
建立基础数据库

选择认证信息存放介质,本文考虑用mysql数据库


mysql 连接信息为:
"com.mysql.jdbc.Driver"
"jdbc:mysql://localhost/test"
下载mysql jdbc驱动
把驱动程序放到
$JBOSS_HOME/server/default/deploy/jbossweb-tomcat55.sar/ 目录下 或 josso src lib 目录下

建立数据库,执行下列SQL
-- Roles
CREATE TABLE JOSSO_ROLE (
NAME VARCHAR(16) NOT NULL,
DESCRIPTION VARCHAR(64) NULL
);
ALTER TABLE JOSSO_ROLE
ADD ( PRIMARY KEY (NAME) ) ;
-- Users
CREATE TABLE JOSSO_USER (
LOGIN VARCHAR(16) NOT NULL,
PASSWORD VARCHAR(20) NOT NULL,
NAME VARCHAR(64) NULL,
DESCRIPTION VARCHAR(64) NULL
);
ALTER TABLE JOSSO_USER
ADD ( PRIMARY KEY (LOGIN) ) ;
-- Users Properties
CREATE TABLE JOSSO_USER_PROPERTY (
LOGIN VARCHAR(16) NOT NULL,
NAME VARCHAR(255) NOT NULL,
VALUE VARCHAR(255) NOT NULL
);
ALTER TABLE JOSSO_USER_PROPERTY
ADD ( PRIMARY KEY (LOGIN, NAME) ) ;
ALTER TABLE JOSSO_USER_PROPERTY
ADD ( FOREIGN KEY (LOGIN)
REFERENCES JOSSO_USER ) ;
-- Roles by user
CREATE TABLE JOSSO_USER_ROLE (
LOGIN VARCHAR(16) NOT NULL,
NAME VARCHAR(255) NOT NULL
);
ALTER TABLE JOSSO_USER_ROLE
ADD ( PRIMARY KEY (LOGIN, NAME) ) ;
ALTER TABLE JOSSO_USER_ROLE
ADD ( FOREIGN KEY (NAME)
REFERENCES JOSSO_ROLE ) ;
ALTER TABLE JOSSO_USER_ROLE
ADD ( FOREIGN KEY (LOGIN)
REFERENCES JOSSO_USER ) ;
-- SSO Sessions
CREATE TABLE JOSSO_SESSION
(
SESSION_ID VARCHAR (64) NOT NULL
, USERNAME VARCHAR (128) NOT NULL
, CREATION_TIME INTEGER NOT NULL
, LAST_ACCESS_TIME INTEGER NOT NULL
, ACCESS_COUNT INTEGER NOT NULL
, MAX_INACTIVE_INTERVAL INTEGER NOT NULL
, VALID INTEGER NOT NULL
);
ALTER TABLE JOSSO_SESSION
ADD ( PRIMARY KEY (SESSION_ID) ) ;

INSERT INTO JOSSO_ROLE (NAME,DESCRIPTION) VALUES('role1','The Role1');
INSERT INTO JOSSO_ROLE (NAME,DESCRIPTION) VALUES('role2','The Role2');
INSERT INTO JOSSO_ROLE (NAME,DESCRIPTION) VALUES('role3','The Role3');
INSERT INTO JOSSO_USER (LOGIN,PASSWORD,DESCRIPTION)
VALUES('user1', 'user1pwd', 'The User1');
INSERT INTO JOSSO_USER_ROLE (LOGIN,NAME) VALUES('user1', 'role1');
INSERT INTO JOSSO_USER_ROLE (LOGIN,NAME) VALUES('user1', 'role2');
INSERT INTO JOSSO_USER (LOGIN,PASSWORD,DESCRIPTION)
VALUES('user2', 'user2pwd', 'The User2');
INSERT INTO JOSSO_USER_ROLE (LOGIN,NAME) VALUES('user2', 'role3');
INSERT INTO JOSSO_USER_PROPERTY(LOGIN,NAME,VALUE)
VALUES('user1', 'user.name', 'User1 Name');
INSERT INTO JOSSO_USER_PROPERTY(LOGIN,NAME,VALUE)
VALUES('user1', 'user.lastName', 'User1 Last Name');
INSERT INTO JOSSO_USER_PROPERTY(LOGIN,NAME,VALUE)
VALUES('user1', 'user.registrationDate', 'User1 Registration Date');
INSERT INTO JOSSO_USER_PROPERTY(LOGIN,NAME,VALUE)
VALUES('user2', 'user.name', 'User2 Name');
INSERT INTO JOSSO_USER_PROPERTY(LOGIN,NAME,VALUE)
VALUES('user2', 'user.lastName', 'User2 Last Name');
INSERT INTO JOSSO_USER_PROPERTY(LOGIN,NAME,VALUE)
VALUES('user2', 'user.registrationDate', 'User2 Registration Date');


----------------------------------------
设置好环境变量

set JAVA_HOME=c:jdk1.5.0_03
set JBOSS_HOME=c:jboss-4.0.3SP1 类似
----------------------------------------
#####################################
设置JOSSO配置文件信息 %JOSSO_HOME%srcresources
1.设置网关配置文件 【
Gateway Configuration】josso-gateway-config.xml
<?xml version="1.0" encoding="ISO-8859-1"?>
<domain>
<name>SampleDomain</name>
<type>web</type>
<authenticator>
<class>org.josso.auth.AuthenticatorImpl</class>
<authentication-schemes>
<!-- Basic Authentication Scheme -->
<authentication-scheme>
<name>basic-authentication</name>
<class>org.josso.auth.scheme.UsernamePasswordAuthScheme</class>
<!--JDBC Credential Store-->
<credential-store>
<class>org.josso.gateway.identity.service.store.db.JDBCIdentityStore </class>
<credentialsQueryString>SELECT login AS username , password AS password FROM josso_user
WHERE login = ?</credentialsQueryString>
<connectionName>cernet</connectionName>
<connectionPassword>password</connectionPassword>
<connectionURL>jdbc:mysql://localhost/cernet</connectionURL>
<driverName>com.mysql.jdbc.Driver</driverName>
</credential-store>
<credential-store-key-adapter>
<class>org.josso.gateway.identity.service.store.SimpleIdentityStoreKeyAdapter </class>
</credential-store-key-adapter>
</authentication-scheme>
</authentication-schemes>
</authenticator>
<sso-identity-manager>
<class>org.josso.gateway.identity.service.SSOIdentityManagerImpl</class>
<!-- JDBC Identity Store -->
<sso-identity-store>
<class>org.josso.gateway.identity.service.store.db.JDBCIdentityStore </class>
<userQueryString>SELECT login FROM josso_user WHERE login = ? </userQueryString>
<rolesQueryString>SELECT josso_role.name FROM josso_role , josso_user_role , josso_user
WHERE josso_user.login = ? AND josso_user.login = josso_user_role.login
AND josso_role.name = josso_user_role.name</rolesQueryString>
<connectionName>cernet</connectionName>
<connectionPassword>password</connectionPassword>
<connectionURL>jdbc:mysql://localhost/cernet</connectionURL>
<driverName>com.mysql.jdbc.Driver</driverName>
</sso-identity-store>
<sso-identity-store-key-adapter>
<class>org.josso.gateway.identity.service.store.SimpleIdentityStoreKeyAdapter</class>
</sso-identity-store-key-adapter>
</sso-identity-manager>
<sso-session-manager>
<class>org.josso.gateway.session.service.SSOSessionManagerImpl</class>
<!--
Set the maximum time interval, in minutes, between client requests
before the SSO Service will invalidate the session. A negative time
indicates that the session should never time out.
-->
<maxInactiveInterval>1</maxInactiveInterval>
<sso-session-store>
<class>
org.josso.gateway.session.service.store.MemorySessionStore
</class>
</sso-session-store>
<sso-session-id-generator>
<class>
org.josso.gateway.session.service.SessionIdGeneratorImpl
</class>
<!--
The message digest algorithm to be used when generating session
identifiers. This must be an algorithm supported by the
java.security.MessageDigest class on your platform.

In J2SE 1.4.2 you can check :
Java Cryptography Architecture API Specification & Reference -
Apendix A : Standard Names
Values are : MD2, MD5, SHA-1, SHA-256, SHA-384, SHA-512
-->
<algorithm>MD5</algorithm>
</sso-session-id-generator>
</sso-session-manager>
<sso-audit-manager>
<class>org.josso.gateway.audit.service.SSOAuditManagerImpl</class>
<handlers>
<!-- This handler logs all audit trails using Log4J, under the given category -->
<handler>
<class>org.josso.gateway.audit.service.handler.LoggerAuditTrailHandler</class>
<name>LoggerAuditTrailHandler</name>
<category>org.josso.gateway.audit.SSO_AUDIT</category>
</handler>
</handlers>
</sso-audit-manager>
<!-- SSO Event Manager component -->
<sso-event-manager>
<class>org.josso.gateway.event.security.JMXSSOEventManagerImpl</class>
<!--
JMX Name of the EventManager MBean that will send SSO Events as JMX Notifications
The MBean will be registered by the MBeanComponentKeeper.
-->
<oname>josso:type=SSOEventManager</oname>
</sso-event-manager>
</domain>

2.设置智能代理配置文件 【Agent Configuration】josso-agent-config.xml
<?xml version="1.0" encoding="ISO-8859-1" ?>
<agent>

<!-- JOSSO Agent classes -->
<!--class>org.josso.tc50.agent.CatalinaSSOAgent</class-->
<!--class>org.josso.tc55.agent.CatalinaSSOAgent</class-->
<!--class>org.josso.jb32.agent.JBossCatalinaSSOAgent</class-->
<class>org.josso.jb4.agent.JBossCatalinaSSOAgent</class>

<!-- Login/Logout URLs -->
<gatewayLoginUrl>http://localhost:8080/josso/signon/login.do</gatewayLoginUrl>
<gatewayLogoutUrl>http://localhost:8080/josso/signon/logout.do</gatewayLogoutUrl>
<!--gatewayLoginErrorUrl>http://localhost:8080/josso/signon/login.do</gatewayLoginErrorUrl-->

<!--
Usefull when working in N-Tier modes behind a reverse proxy or load balancer
Here you should place the reverse proxy or load balancer base URL.

Note : When using this options, the gatewayLoginURL and gatewayLogoutURL should also point to this host.

<singlePointOfAccess>http://reverse-proxy-host:8080</singlePointOfAccess>

<gatewayLoginUrl>http://reverse-proxy-host:8080/josso/signon/login.do</gatewayLoginUrl>
<gatewayLogoutUrl>http://reverse-proxy-host:8080/josso/signon/logout.do</gatewayLogoutUrl>
-->

<!-- Mininum interval between sso session access , in milliseconds -->
<sessionAccessMinInterval>1000</sessionAccessMinInterval>

<!-- JOSSO Agent service locator configuration -->
<service-locator>
<class>org.josso.gateway.WebserviceGatewayServiceLocator</class>
<endpoint>localhost:8080</endpoint>

<!-- Associate an identity to SOAP messages
<username>wsclient</username>
<password>wsclientpwd</password>
-->

<!-- Enabled SSL on the SOAP circuit.
<transportSecurity>confidential</transportSecurity>
-->
</service-locator>

<!--
JOSSO Parnter application definicions :

Configure all web applications that should be a josso partner application within this server.
For each partner application you have to define the propper web-context.
-->
<partner-apps>

<partner-app>
<context>/partnerapp</context>
<!-- This is an optional feature :
You can reference any web resource collection that should not be subject to SSO protection.
The SSO agent will not provide identity nor demand authentication to requests matching the
security constraint associated to this web resource collections.
In order to work, the security constraint must not contain auth-constraints declarations.
See sample web.xml file from josso partnerapp.
<security-constraint>
<ignore-web-resource-collection>public-resources</ignore-web-resource-collection>
</security-constraint>
-->
</partner-app>

</partner-apps>

</agent>


3.设置 josso-reverseproxy-config.xml 配置文件

4.设置 josso配置文件 josso-config.xml
<?xml version="1.0" encoding="ISO-8859-1" ?>
<configuration>
<hierarchicalXml fileName="josso-gateway-config.xml"/>
<hierarchicalXml fileName="josso-agent-config.xml"/>
<hierarchicalXml fileName="josso-reverseproxy-config.xml"/>
</configuration>

#####################################################

配置应用服务器文件

----------------------------------------

编辑server.xml $JBOSS_HOME/server/default/deploy/jbossweb-tomcat55.sar/server.xml

<Server>
...
<Service>
...
<Engine>
...
<Host name="localhost" ...>
...
<Valve className="org.josso.tc55.agent.SSOAgentValve" debug="1"/>
...
</Host>
</Engine>
</Service>
</Server>


<Server>
...
<Service>
...
<Engine name="Catalina" defaultHost="localhost" debug="0">
...
<Realm className="org.josso.jb4.agent.JBossCatalinaRealm"
appName="josso"
userClassNames="org.josso.gateway.identity.service.BaseUserImpl"
roleClassNames="org.josso.gateway.identity.service.BaseRoleImpl"
debug="1" />
...
</Engine>
</Service>
</Server>

----------------------------------------
编辑 login-config.xml $JBOSS_HOME/server/default/conf

<application-policy name = "josso">
<authentication>
<login-module code = "org.josso.jb4.agent.JBossSSOGatewayLoginModule"
flag = "required">
<module-option name="debug">true</module-option>
</login-module>
</authentication>
</application-policy>

拷贝文件到$JBOSS_HOME/server/default/conf
josso-config.xml
josso-gateway-config.xml
josso-agent-config.xml
josso-reverseproxy-config.xml

#########################################
执行 Ant Build 任务列表部署和启动JOSSO on JBOSS
----------------------------------------
//编译War包
build.bat war
----------------------------------------
//安装josso到jboss
build.bat install-jboss4

----------------------------------------
//部署 josso应用ear包
build.bat deploy-jboss4
----------------------------------------
//启动 Jboss 进程
cd $JBOSS_HOME/bin
cd %JBOSS_HOME%bin
run.bat
----------------------------------------
访问受保护地址验证SSO
http://localhost:8080/partnerapp/protected
user and password is : user1/user1pwd user2/user2pwd
----------------------------------------


########################################
错误诊断

15:30:15,922 ERROR [UsersRolesLoginModule] Failed to load users/passwords/role files
错误,一般是因为 login-config.xml 没有设置

星期四, 三月 01, 2007

JSR

89/90/91/130/142/144/210/251/254/263/265/285

Download OSS Service Activation API (See also JSR-000089 Web Page)

Download OSS Quality of Service API (See also JSR-000090 Web Page)

Download OSS Trouble Ticket API (See also JSR-000091 Web Page)

Download OSS Billing Mediation API (See also JSR-000130 Web Page)

Download OSS Inventory API (See also JSR-000142 Web Page)

Download OSS Common API (See also JSR-000144 Web Page)

Download OSS Service Quality Management API (See also JSR-000210 Web Page)

Download Pricing API (See also JSR-000251 Web Page)

Download OSS Discovery API (See also JSR-000254 Web Page)

Download Fault Management API (See also JSR-000263 Web Page)

Download Order Management API (See also JSR-000264 Web Page)

Download Performance Management API (See also JSR-000285 Web Page)

星期一, 二月 26, 2007

NGOSS SID 发表 7.0版本

这次发布的版本,更新和细化了两个主要的业务模型:产品,收入保障

正在看产品模型,可以说完全引入了amdocs,siebel等大厂商的核心产品,商品,定购,类目管理,产品包,价格模型等概念,基本上能和传统的CRM产品模型吻合。

价格策略和产品订购的价格和优惠还得细细研读,这块不熟,可是计费模型的核心。

星期五, 二月 09, 2007

安永的企业家精神的四个考量指标


转自 江南春的博客


1)对企业和个人设定一个高标准并坚定不移地执行和实现;
2)能够证明其克服了困难和障碍;
3)遭受过巨大的失败并且从失败中吸取教训;
4)既能信任团队,又能在不确定性前独立思考。

星期四, 二月 08, 2007

需求中的逻辑实体关系设计主要为了什么




  • 理清系统中的实体,实体属性,关联,作用域信息




  • 将需求细化到不可分割的实体属性,如果实体的属性还有相关描述和范围,还需将属性提升到实体




  • 明确实体间关系和约束,建立明确的关联关系,依此来避免遗漏需求




  • 明确约束的必要性原则,区分强关联和弱关联,保证系统完整性和健壮性




  • 有机划分逻辑域 ,相同功能的实体归并到同一个域,域之间建立较少的弱关联,有利于组件化和模块化




星期三, 一月 31, 2007

Microsoft Releases AJAX Tool to the Web

NND,M$老是慢半拍(老是先引发战争然后收拾残局),可这步棋子下的又正是时候,这应该标志着AJAX和富Web的推广已经到一个阶段了。大家可以不用担心AJAX的前景了,AJAX已经成为必需。


http://ajax.asp.net/


http://www.eweek.com/article2/0,1895,2086704,00.asp?kc=EWWSUEMNL012407EOAD




圈子真的很小

哈哈,IT圈子真的很小,中午吃工作餐,四位原来合力的老同事又碰头了(最近差不多碰到了八九位合力的老同事),现在大家分属两家公司。做的业务也不尽相同,但大家感触都差不多;结婚生子,工作生活,堵车与开车,行业发展,公司前景。


抽取几段聊天心得:




  1. 小孩睡觉得养成好习惯,不然天天半夜闹你起床;




  2. 北京还是坐公共交通好,开车上下班费钱又费时;




  3. 3G要来了,大家都在努力准备,软件公司业务和产品的积淀是关键;




  4. 开三轮车拉活的比我们赚的多;




  5. BI和CRM该是今后电信软件建设的关键;




  6. 努力让老婆在家附近找个好工作;




  7. 移动独大的日子不久就结束了,话费估计会下调了,以后还会有固定电话吗?




  8. 电信软件公司不好过,减薪增效,按效计酬成了落后公司的风俗;奖金优厚,人才集中,天天加班也成了先进公司的习惯;优胜劣汰一直在继续




  9. 努力赚钱,多拿奖金,少加班是大家的心愿。^_^



IBM OmniFind Yahoo! Edition试用手记

IBM OmniFind + Yahoo! ?


http://www-306.ibm.com/software/data/enterprise-search/omnifind-enterprise/features.html


http://omnifind.ibm.yahoo.net/


试用以后,功能比较单一,但亮点不少:




  • 可以建立对某个网站的全文搜索(支持中日韩等国双字节文字索引)




  • 提供对加密网站的访问和蜘蛛索引抓取(感觉很棒)




  • 可以搜索本地文件




  • 搜索的文件类型比较齐全,但不可以自定义文件类型




  • 搜索结果集成展示,有Cached和Html模式浏览




  • 可以设定网络蜘蛛抓取频率和深度,可以设定 Rank




  • 抓取速度比较低,索引库占有磁盘空间比较大(相比Copernic Desktop Search和Google Desktop)




  • 应该会预留类似 IBM OmniFind Enterprice 的多系统接口,对接其他企业系统(Lotus Document,Portal,...)




  • 只能提供最多到5万文档级别的索引库容量




总体感觉,对中小企业很适合,比较适合企业内部KM应用体制的初期建立,但真正的知识分类,分级,安全,知识提炼的功能还是没有或说很弱。



e书,免费下载及其他



今天收到Bookvisions的邮件,通知说被迫停办已久的Bookvisions英文电子书网站重新开放了。



域名改为了:www.proboox.com ,登录该网站发现,我原有的用户资料和积分还存在,真的谢谢站长阿,又可以方便的浏览最新英文书籍了。




其实现在免费获取电子书籍和论文杂志的手段不少,我现在一般都用电驴,还有www.itepub.com www.chmpdf.com www.itpub.net 等不少国内的网站,偶尔会去国图电子阅览室下载。但我更喜欢Bookvisions网站的模式,它有清晰的分类,很好的图书质量把关,而且限定在最新出版的英文书籍上,没有弹出广告和流氓软件的烦扰。



不过大多数人,包括我自己,都是好读书,不求甚解;下了好多资料,真正专心研读的却只是凤毛麟角,希望这次Bookvisons能多坚持一段时间,也希望自己能静下心来好好读一两本专业的书籍(计划限定在NGN,IP网络和协议,CRM和电信领域)。



阿门。。。



星期二, 九月 05, 2006

一些想法

又开始一个计划了,俗话说“凡事预则立,不预则废”,可做才是最重要的。
网络瞬息万变,技术主导一切,内容主宰财富。
现今的网络业,概念不缺,创意不缺,但真正坚持的忍者有几多,163、Sina、Sohu、Alibaba、IT168、ITPub、IT、Blogchina、BJUG/Javaeyes。经过了几年的发展,都有了长足进步。
坚持,总是最后的胜者,概念和创意有可能冲昏头脑,但坚持是始终必须紧握的权杖。

客户中心,用户中心,体验经济,内部传播。物质和精神财富的丰富,人越来越崇尚展现自我,福祉社会。共产已被世界上大多数的先进者接受。盖茨,默多克,李嘉诚....和谐共赢,人民政权,民主政治;也越来越是广大人民的政治和政权了。。

民心所向,已是这10年内网络业的指导和努力方向。广告传媒,电子商务,基础资源提供,内容提供,Hosted(ASP),技术服务、知识库、二手市场,零售网店,网上银行和证券炒汇等,无不为终端客户的意愿为顶礼膜拜的对象。

人类,群体,社会的思想瞬息万变,互联网络业也必然随者人类不断变迁的思想,努力适应。高强度,高智利,高风险,高投入,亚健康;始终伴随着这个行业。

我所想,1999-2002这个行业正处在火山爆发的前夜,抑或冰川时代的终结,抑或水乳交融的瞬间。而02年后到现在的持续爆发,已经让大地形成了一层肥沃的火山灰层,勤劳的第二代网络人,耕耘者自己的那块希望和憧憬。
人民已经可以看到了收获的希望。时代翻开了新的一页,不需回望过去,前面的路有千万条,选一条合适自己的,一步一个脚印,走下去吧。。。

星期四, 八月 31, 2006

几点,转

关于钱



  • 不用VC


  • 从第一天开始做财务


  • 盈亏平衡在任何时候都是重要的




关于商业




  • 只做上升期的行业

  • 关注中线增长率

  • 不劳动有回报的是生意。不劳动有增长的是好生意。劳动仅仅是加快增长

  • 有长期观念,用逻辑和分析指导行动



关于人



  • 人一定要少,不盲目扩张


  • 长期做事,要过好日子


原始地址:
http://feeds.feedburner.com/~r/wangjianshuo/~3/9200543/20060804_aecc.htm

星期四, 八月 10, 2006

Terminology and Acronym Glossary (Enhanced Telecom Operations Map? (eTOM) )

Terminology
==========================
Complementary Provider
The Complementary Provider provides additional products and services to extend the attractiveness of an enterprise’s products and services and scope of its of the value network. Frequently, these products and services are co-branded.

Customer

The Customer buys products and services from the Enterprise or receives free offers or services. A Customer may be a person or a business.

Customer Operations Process

A Customer Operations Process is an end-end process that focuses totally on directly supporting Customer needs, i.e., Fulfillment, Assurance or Billing. It may be initiated by the Customer or be initiated by the Service Provider.

e-business

e-business includes the Internet presence and buy and sell transaction over digital media of e-commerce. It also includes the integration of front- and back-office processes and applications to provide support and bill for the product or service. For the eTOM framework it is even more expansive. e-business is the integration of traditional business models and approaches with e-business opportunities.

e-commerce

e-commerce is Internet presence and business buying and selling transactions over digital media.

End-to-End Process Flow

End-to-end process flow includes all sub-processes and activities and the sequence required to accomplish the goals of the process. Note that the top-level views of the eTOM framework do NOT show end-to-end process flow since there is no indication of sequence. The eTOM framework shows end-to-end process groupings (see definition below)
The end-to-rend, customer processes recognized in the eTOM framework are generic sequences of activities that need to occur in the enterprise to achieve desired results. (i.e. they are not specific to a particular ICSP Business, Product, Channel or Technology).
The eTOM framework does not direct or constrain the way end-to-end processes can be implemented, rather it only guides the definition of standardized process elements to be used within the enterprise. In this way process elements can be assembled for a specific service provider’s end-to-end process requirements. The eTOM framework does not mandate a single way the process elements should be organized or sequenced to create end-to-end processes.

End-to-End Process Grouping

The top-level view of the eTOM framework shows end-to-end process groupings. At this level of the process framework, flow is not appropriate. However, these groupings represent processes that have end-to-end results that are key measures for the enterprise.
Also termed as vertical process grouping(s).

End User

The End User is the actual user of the Products or Services offered by the Enterprise. The end user consumes the product or service. See also Subscriber below.

Enterprise


Enterprise is used to refer to the overall business, corporation or firm, which is using the eTOM framework for modeling its business processes. The enterprise is responsible for delivering products and services to the Customer. It is assumed that the enterprise is an Information or Communications Service Provider (see ICSP explanation below).

Enterprise Management Process Grouping

This Process grouping involves the knowledge of Enterprise-level actions and needs, and encompasses all Business Management functionalities necessary to support the operational processes, which are critical to run a business in the competitive market. These are sometimes thought of as corporate processes and support. Some functions such as for Enterprise Risk Management (e.g. security and fraud management) have to be more tailored to Information and Communications Service Providers, but most (e.g., Financial Management, Public Relations) are not significantly different for the ICSP industry.

我顶你个肺,CRM也2.0 !!!!!

Gartner老祖又开始忽悠了.提出了2.0CRM的设想,密切关注这次会议.)

Gartner Customer Relationship Management Summit
CRM 2.0: Managing the New Customer Experience 
 
 
 11-13 September 2006
Chicago, IL
Chicago Hilton and Towers

What You Will Learn In this Summit:

  1. The benefits of a customer-centric organization
  2. The latest trends for customer strategies and technologies
  3. How to create a single view of the customer
  4. How to improve marketing, sales and customer service processes
  5. How to manage the customer experience
  6. Which vendors and solutions to consider for different aspects of CRM
  7. When to consider CRM Ondemand as a delivery option
  8. How new technologies (VoIP, Gaming, Interactive TV) impact your CRM initiatives
  9. What organizational and cultural changes must happen to ensure success

互联网经济本质上是一种信心经济

互联网的自发性,主动性和非垄断性决定了他永远是用户为导向的经济。任何组织和个人想在这个区域搞垄断和专狠,必定行不通。以互联网为主要盈利区域的公司,应该始终恪守客户为中心的理念,约束和规范企业盈利行为,建立信任经济。

CRM2.0也应该可以包括这一块,如何在网络上营造信任经济模式。

http://www.iab.net/standards/

http://feeds.feedburner.com/~r/PlayinWithIt/~3/9628640/990700.aspx


blogspot 大陆可以访问。

不知道什么时候还要封。。抓紧时间浏览一下。。

估计Google也根据本地政府政策对内容进行了过滤。。文本过滤技术越来越成为搜索引擎和内容提供商的必须。

有感于学术造假和发文章有奖

钱是绝对不能乱给的,学术需要自由,交流,提升和菁华;光想着钻空子搂钱作买卖,那不和卖菜的大妈差不多了吗。

学术是严谨的,1个成果需要历经1年到几年的实践才可以有方法,有成果;光去投其所好的发表论文,耽误了研究时间,又毁了职业道路。

感觉中国又回到了大跃进时代。。

http://yanfeng.org/blog/841/

cybercorlin

cybercorlin