JD Edwards ERP has 3 areas of expertise: 1. Functional - Business Analyst, 2. Technical Programmer - Developer and 3. CNC - System Administrator and Architect.
1. Functional - Business Analyst
Business subject matter expert on one or more of the JD Edwards modules (Financials, Manufacturing, Transportation, Sales, etc...) often they started as a JDE user, the power user and gradually developed the skill to support the business aspects of JDE. Else, they might have a business degree and come into JDE on the job as a Business Analyst. Functional person seldom has any programming or development experience.
2. Technical Programmer - Developer
Developers are trained in the software development and programming tools that translate the business requirements as identified by the functional into programming code. Sometimes these individuals simply modify existing JDE objects and in other cases, develop entire suites of applications using EnterpriseOne development tools including the Report Design Aide (RDA), Table Design Aide (TDA), Business Function C-code design tools and others using JDE's Change Management System, Object Management Workbench.
3. CNC - System Administrator and Architect
Configurable Network Computing or CNC is a catch-all function comprising all that the two positions above do not cover including, Installation, Upgrades, Migrations, Updates, Change Management, System Administration, Security, Performance Tuning, Package Build and Deployment and over-all Architecture. CNC also refers to the systems analysts who install, maintain, manage and enhance the JD Edwards ERP architecture.
The CNC title is taken from the term ‘Configurable Network Computing’ which describes the overall JDE architecture combining mixed hardware, operating systems and databases to work together seamlessly. CNC technology continues to be at the heart of JD Edwards EnterpriseOne architecture and will play a significant role Oracle's Fusion Architecture initiative. Now a division of the Oracle Corporation, CNC is JD Edwards's client-server proprietary architecture and methodology that implements its highly-scalable enterprise-wide business solutions software that can run on a wide variety of hardware, operating systems and hardware platforms.
Saturday, May 16, 2009
Friday, May 15, 2009
Security Policy
Security policies are an absolute must ground-work for any organization providing the virtual glue to hold it all together. Before we begin about policies, let’s talk a little about trust as a central theme in many policies. Some policies may not be written because there is trust that people will do the right thing but needed because people don't always do the right thing. Ideally you want to trust all resources, but that is unrealistic. Buggy hardware and software are commonplace. Try to implement controls and procedures to minimize the impact when a failure does occur. Trust of employees and users develops over time. Different categories of employees should be trusted at different levels ensuring level of access is commensurate with level of trust.
When looking at trust, you have three basic models: 1. Trust everyone 2. Trust no one and 3. Trust some people at some time. In today's world it is not very common to find organizations that follow the model of trusting everyone all of the time or trusting no one at any time. The most common model is to trust some people some of the time and build trust over time. Also keep in mind that it may be appropriate to apply different trust models to different parts of the organization.
My experience in the field has consistently shown that security policies tend to elevate the level of tension in any given situation with the fact that people don’t like rules and restrictions in their activities. Everyone tends to view security needs differently: 1. Users are concerned about being able to get their work done without a lot of controls. 2. System support personnel are concerned about the ease of managing systems under tight control. 3. Management is concerned about costs versus protection. Getting all to agree of a policy is impossible so best is to try a Win-Win compromise.
To some extent everyone should be concerned of security policies as everyone is affected by them. The system users are typically affected the most as they see the policies as a set of rules to regulate their behavior making it more difficult for them to accomplish their job. The people who have to support the infrastructure are concerned since they are the ones who have to implement and comply by many of the policies. For example, a policy that requires all Windows Servers to be installed according to a baseline security standard would require more work on the part of the system administrators, not only for the initial install, but also for the system upkeep.
When planning policies, some organizations will go overboard and come up with something that will be impossible to implement and comply with. The bottom line for policies is they must take into consideration the balance of protection with the level of productivity hit. Policies should be concise and easy to read and understand. One thing to keep in mind when developing a policy is how it will affect legacy systems and other infrastructure that is already in place. Once the policies are fully approved, they should be made available to all users who are affected. Finally, all policies should be updated to reflect changes in organization or culture.
One of the major goals of a policy is to implement control. Deciding on the level of control for a specific policy is not always clear-cut. The security needs and the culture of the organization will play a major role when deciding what level of control is appropriate. If you make policies too restrictive or too hard to implement and comply with, they will either be ignored (not implemented) or people will find a way to circumvent the controls in the policies.
When looking at trust, you have three basic models: 1. Trust everyone 2. Trust no one and 3. Trust some people at some time. In today's world it is not very common to find organizations that follow the model of trusting everyone all of the time or trusting no one at any time. The most common model is to trust some people some of the time and build trust over time. Also keep in mind that it may be appropriate to apply different trust models to different parts of the organization.
My experience in the field has consistently shown that security policies tend to elevate the level of tension in any given situation with the fact that people don’t like rules and restrictions in their activities. Everyone tends to view security needs differently: 1. Users are concerned about being able to get their work done without a lot of controls. 2. System support personnel are concerned about the ease of managing systems under tight control. 3. Management is concerned about costs versus protection. Getting all to agree of a policy is impossible so best is to try a Win-Win compromise.
To some extent everyone should be concerned of security policies as everyone is affected by them. The system users are typically affected the most as they see the policies as a set of rules to regulate their behavior making it more difficult for them to accomplish their job. The people who have to support the infrastructure are concerned since they are the ones who have to implement and comply by many of the policies. For example, a policy that requires all Windows Servers to be installed according to a baseline security standard would require more work on the part of the system administrators, not only for the initial install, but also for the system upkeep.
When planning policies, some organizations will go overboard and come up with something that will be impossible to implement and comply with. The bottom line for policies is they must take into consideration the balance of protection with the level of productivity hit. Policies should be concise and easy to read and understand. One thing to keep in mind when developing a policy is how it will affect legacy systems and other infrastructure that is already in place. Once the policies are fully approved, they should be made available to all users who are affected. Finally, all policies should be updated to reflect changes in organization or culture.
One of the major goals of a policy is to implement control. Deciding on the level of control for a specific policy is not always clear-cut. The security needs and the culture of the organization will play a major role when deciding what level of control is appropriate. If you make policies too restrictive or too hard to implement and comply with, they will either be ignored (not implemented) or people will find a way to circumvent the controls in the policies.
Tuesday, April 28, 2009
Hitler and CNC
I found this hilarious video on JD Edwards CNC, hoping you all enjoy it too. Kindly read the subtitles.
JD Edwards E1 Complete Reference
Authors: Allen Jacot, Joseph Miller, Michael Jacot, John SternYour definitive guide to JD Edwards EnterpriseOne. Implement and maintain a fully integrated, SOA-based ERP framework across your entire corporation. JD Edwards EnterpriseOne: The Complete Reference explains how to install and administer JD Edwards EnterpriseOne, store BI information in data marts and warehouses, manage servers and portals, and develop customized applications and kernel processes. You'll also learn how to create and distribute packages, use the security workbench, optimize performance, and apply the latest JD Edwards EnterpriseOne updates and tools releases.
Set up and configure the JD Edwards EnterpriseOne applications suite. Work with Oracle, SQL Server, DB2, MSDE, and SSE data sources. Define JD Edwards EnterpriseOne path codes, task views, and environments. Deploy the object configuration manager and solution explorer. Build client and server packages, media objects, and data warehouses. Secure JD Edwards EnterpriseOne using LDAP, single sign-on, and third-party tools. Administer portals and Web sites using JD Edwards EnterpriseOne's HTML server and server manager. Troubleshoot and tune your system using the performance workbench.
Covers Release 8.12.
Monday, April 27, 2009
Oracle buys Sun
Redwood Shores, CA - April 20, 2009
Oracle Corporation (NASDAQ: ORCL) and Sun Microsystems (NASDAQ: JAVA) announced today they have entered into a definitive agreement under which Oracle will acquire Sun common stock for $9.50 per share in cash. The transaction is valued at approximately $7.4 billion, or $5.6 billion net of Sun’s cash and debt. “We expect this acquisition to be accretive to Oracle’s earnings by at least 15 cents on a non-GAAP basis in the first full year after closing. We estimate that the acquired business will contribute over $1.5 billion to Oracle’s non-GAAP operating profit in the first year, increasing to over $2 billion in the second year. This would make the Sun acquisition more profitable in per share contribution in the first year than we had planned for the acquisitions of BEA, PeopleSoft and Siebel combined,” said Oracle President Safra Catz.
“The acquisition of Sun transforms the IT industry, combining best-in-class enterprise software and mission-critical computing systems,” said Oracle CEO Larry Ellison. “Oracle will be the only company that can engineer an integrated system – applications to disk – where all the pieces fit and work together so customers do not have to do it themselves. Our customers benefit as their systems integration costs go down while system performance, reliability and security go up.”
There are substantial long-term strategic customer advantages to Oracle owning two key Sun software assets: Java and Solaris. Java is one of the computer industry’s best-known brands and most widely deployed technologies, and it is the most important software Oracle has ever acquired. Oracle Fusion Middleware, Oracle’s fastest growing business, is built on top of Sun’s Java language and software. Oracle can now ensure continued innovation and investment in Java technology for the benefit of customers and the Java community.
The Sun Solaris operating system is the leading platform for the Oracle database, Oracle’s largest business, and has been for a long time. With the acquisition of Sun, Oracle can optimize the Oracle database for some of the unique, high-end features of Solaris. Oracle is as committed as ever to Linux and other open platforms and will continue to support and enhance our strong industry partnerships.
“Oracle and Sun have been industry pioneers and close partners for more than 20 years,” said Sun Chairman Scott McNealy. “This combination is a natural evolution of our relationship and will be an industry-defining event.”
“This is a fantastic day for Sun’s customers, developers, partners and employees across the globe, joining forces with the global leader in enterprise software to drive innovation and value across every aspect of the technology marketplace,” said Jonathan Schwartz, Sun’s CEO, “From the Java platform touching nearly every business system on earth, powering billions of consumers on mobile handsets and consumer electronics, to the convergence of storage, networking and computing driven by the Solaris operating system and Sun’s SPARC and x64 systems. Together with Oracle, we’ll drive the innovation pipeline to create compelling value to our customer base and the marketplace.”
“Sun is a pioneer in enterprise computing, and this combination recognizes the innovation and customer success the company has achieved. Our largest customers have been asking us to step up to a broader role to reduce complexity, risk and cost by delivering a highly optimized stack based on standards,” said Oracle President Charles Phillips. “This transaction will preserve and enhance investments made by our customers, while we continue to work with our partners to provide customers with choice.”
The Board of Directors of Sun Microsystems has unanimously approved the transaction. It is anticipated to close this summer, subject to Sun stockholder approval, certain regulatory approvals and customary closing conditions.
There will be a conference call today to discuss the transaction at 5:30 a.m. Pacific time. Investors can listen to the conference call by dialing (719) 234-7870, passcode 923645. A replay will be available for 24 hours after the call ends at (719) 884-8882, passcode: 923645. A live audio webcast of the call will be made available at www.oracle.com/investor and a replay will be available for seven days after the call ends.
About Sun Microsystems
Sun Microsystems, Inc. (NASDAQ: JAVA) develops the technologies that power the global marketplace. Guided by a singular vision -- "The Network is the Computer" -- Sun drives network participation through shared innovation, community development and open source leadership. Sun can be found in more than 100 countries and on the Web at http://www.sun.com/.
About Oracle
Oracle (NASDAQ: ORCL) is the world's largest enterprise software company. For more information about Oracle, please visit our Web site at http://www.oracle.com/
Oracle Corporation (NASDAQ: ORCL) and Sun Microsystems (NASDAQ: JAVA) announced today they have entered into a definitive agreement under which Oracle will acquire Sun common stock for $9.50 per share in cash. The transaction is valued at approximately $7.4 billion, or $5.6 billion net of Sun’s cash and debt. “We expect this acquisition to be accretive to Oracle’s earnings by at least 15 cents on a non-GAAP basis in the first full year after closing. We estimate that the acquired business will contribute over $1.5 billion to Oracle’s non-GAAP operating profit in the first year, increasing to over $2 billion in the second year. This would make the Sun acquisition more profitable in per share contribution in the first year than we had planned for the acquisitions of BEA, PeopleSoft and Siebel combined,” said Oracle President Safra Catz.
“The acquisition of Sun transforms the IT industry, combining best-in-class enterprise software and mission-critical computing systems,” said Oracle CEO Larry Ellison. “Oracle will be the only company that can engineer an integrated system – applications to disk – where all the pieces fit and work together so customers do not have to do it themselves. Our customers benefit as their systems integration costs go down while system performance, reliability and security go up.”
There are substantial long-term strategic customer advantages to Oracle owning two key Sun software assets: Java and Solaris. Java is one of the computer industry’s best-known brands and most widely deployed technologies, and it is the most important software Oracle has ever acquired. Oracle Fusion Middleware, Oracle’s fastest growing business, is built on top of Sun’s Java language and software. Oracle can now ensure continued innovation and investment in Java technology for the benefit of customers and the Java community.
The Sun Solaris operating system is the leading platform for the Oracle database, Oracle’s largest business, and has been for a long time. With the acquisition of Sun, Oracle can optimize the Oracle database for some of the unique, high-end features of Solaris. Oracle is as committed as ever to Linux and other open platforms and will continue to support and enhance our strong industry partnerships.
“Oracle and Sun have been industry pioneers and close partners for more than 20 years,” said Sun Chairman Scott McNealy. “This combination is a natural evolution of our relationship and will be an industry-defining event.”
“This is a fantastic day for Sun’s customers, developers, partners and employees across the globe, joining forces with the global leader in enterprise software to drive innovation and value across every aspect of the technology marketplace,” said Jonathan Schwartz, Sun’s CEO, “From the Java platform touching nearly every business system on earth, powering billions of consumers on mobile handsets and consumer electronics, to the convergence of storage, networking and computing driven by the Solaris operating system and Sun’s SPARC and x64 systems. Together with Oracle, we’ll drive the innovation pipeline to create compelling value to our customer base and the marketplace.”
“Sun is a pioneer in enterprise computing, and this combination recognizes the innovation and customer success the company has achieved. Our largest customers have been asking us to step up to a broader role to reduce complexity, risk and cost by delivering a highly optimized stack based on standards,” said Oracle President Charles Phillips. “This transaction will preserve and enhance investments made by our customers, while we continue to work with our partners to provide customers with choice.”
The Board of Directors of Sun Microsystems has unanimously approved the transaction. It is anticipated to close this summer, subject to Sun stockholder approval, certain regulatory approvals and customary closing conditions.
There will be a conference call today to discuss the transaction at 5:30 a.m. Pacific time. Investors can listen to the conference call by dialing (719) 234-7870, passcode 923645. A replay will be available for 24 hours after the call ends at (719) 884-8882, passcode: 923645. A live audio webcast of the call will be made available at www.oracle.com/investor and a replay will be available for seven days after the call ends.
About Sun Microsystems
Sun Microsystems, Inc. (NASDAQ: JAVA) develops the technologies that power the global marketplace. Guided by a singular vision -- "The Network is the Computer" -- Sun drives network participation through shared innovation, community development and open source leadership. Sun can be found in more than 100 countries and on the Web at http://www.sun.com/.
About Oracle
Oracle (NASDAQ: ORCL) is the world's largest enterprise software company. For more information about Oracle, please visit our Web site at http://www.oracle.com/
Subscribe to:
Posts (Atom)
