OFBiz Tutorial which will discuss the basic steps of implementing an Apache OFBiz framework for your enterprise eCommerce company. Apache OFBiz is an open source software project from the Apache Software Foundation. OFBiz is a competitive and economical alternative to commercial ERP and eCommerce products.
Implementation in Phases | OFBiz Tutorials
OFBiz software is made up of a complete set of enterprise eCommerce and ERP applications. The OFBiz data model allows for accounting for everything that is happening in a given legacy system and integration of needed components which facilitates a phased approach.
OFBiz has the ability to be implemented gradually while working with older systems and eventually phasing them out.
Affordability and Customization | OFBiz Tutorials
Many commercial ERP software packages are sorely lacking in flexibility. Because of the OFBiz open source system, it is highly adaptable for any users needs and requirements. Configuring software to meet your company rather that configuring your company to fit software will save countless time and money. Also, because OFBiz is open source, you will not be locked into recurring licensing fees.
Enterprise eCommerce using OFBiz can be implemented entirely by HotWax Media. We offer the full spectrum of enterprise eCommerce and ERP implementation tools. Our developers are closely involved with the OFBiz project and have the expertise and dedication needed to make your eCommerce platform robust and effective while offering some of the lowest costs industry wide.
Tuesday, June 22, 2010
Friday, June 18, 2010
OFBiz Tutorials - User Permissions Part 2
OFBiz Tutorials are a free service provided by HotWax Media in order to give OFBiz users more information on how to use their software, as well as giving valuable insight as to why OFBiz is a great solution for enterprise eCommerce.
In this post I will continue to discuss user permissions for Apache OFBiz.
In my initial post on user permissions we discussed giving user permission to access a particular application as well as the various levels of permission available. Depending on the user you can allow them only to view the application, have full administrative access or levels in between (e.g. creating, updating, or deleting records etc.).
Admin permission gives a particular user full access to view, create, update and delete records in a given application.
A single user can be assigned permissions to several applications giving you the flexibility to utilize the employee across a variety of projects, giving them just the amount of permissions that they need.
There are instances where a user has admin permission, yet they are not allowed to perform certain operations within the application based on permissions in other applications. For example, you may be attempting to view a product look up screen in the "Asset Maint" app but in order to do that you also need permission in the "Catalog" application.
The solution for not having to grant permission to an entire additional application is by defining ECA (Event Condition Access) rules that will extend user permission allowing the user to view the selected files in the "Catalog" application while logged into the "Asset Maint" application (of course this can be done for any app, "Asset Maint" and "Catalog" are simply examples).
The rule is defined in a file found under the "servicedef" folder in the component directory tree.
Now, whenever the user attempts to perform a catalog related operation in the "Asset Maint" app, the "catalogpermissioncheck" will run first. If a user does not have explicit permission a "haspermission" flag will come up as false. This is a generic interface used by permission services.
With the permission modifications, the "haspermission" interface will run the check from the "Asset Maint" permissions and see that from that application, the user can view aspects of the "Catalog" application. The "haspermission" flag will come back as true.
To view pathways, go to: http://www.hotwaxmedia.com/apache-ofbiz-blog/ofbiz-tutorial-how-to-use-eca’s-to-extend-service-permission/
Enterprise eCommerce is a powerful means of business in the 21st century. The growth potential is higher than any other form of commerce and offers the ability to reach customers all over the world 24 hours a day.
In this post I will continue to discuss user permissions for Apache OFBiz.
In my initial post on user permissions we discussed giving user permission to access a particular application as well as the various levels of permission available. Depending on the user you can allow them only to view the application, have full administrative access or levels in between (e.g. creating, updating, or deleting records etc.).
Admin permission gives a particular user full access to view, create, update and delete records in a given application.
A single user can be assigned permissions to several applications giving you the flexibility to utilize the employee across a variety of projects, giving them just the amount of permissions that they need.
There are instances where a user has admin permission, yet they are not allowed to perform certain operations within the application based on permissions in other applications. For example, you may be attempting to view a product look up screen in the "Asset Maint" app but in order to do that you also need permission in the "Catalog" application.
The solution for not having to grant permission to an entire additional application is by defining ECA (Event Condition Access) rules that will extend user permission allowing the user to view the selected files in the "Catalog" application while logged into the "Asset Maint" application (of course this can be done for any app, "Asset Maint" and "Catalog" are simply examples).
The rule is defined in a file found under the "servicedef" folder in the component directory tree.
Now, whenever the user attempts to perform a catalog related operation in the "Asset Maint" app, the "catalogpermissioncheck" will run first. If a user does not have explicit permission a "haspermission" flag will come up as false. This is a generic interface used by permission services.
With the permission modifications, the "haspermission" interface will run the check from the "Asset Maint" permissions and see that from that application, the user can view aspects of the "Catalog" application. The "haspermission" flag will come back as true.
To view pathways, go to: http://www.hotwaxmedia.com/apache-ofbiz-blog/ofbiz-tutorial-how-to-use-eca’s-to-extend-service-permission/
Enterprise eCommerce is a powerful means of business in the 21st century. The growth potential is higher than any other form of commerce and offers the ability to reach customers all over the world 24 hours a day.
Friday, June 11, 2010
OFBiz Tutorial - Poject Management
OFBiz tutorial where we will discuss project management options for OFBiz as well as other software platforms. Partnerships are the cornerstone of solid project management. Contributors need to work well together, have congruous visions of the project and the professionalism to carry everything out. Project management tools are necessary for maintaining a successful and efficient company.
HotWax Media has reviewed several project management packages. Our aim being to solve project management and work flow difficulties. In collaboration with our managed hosting partner, Contegix, we discovered the Atlassian suite of tools. Contegix gave the stamp of approval and we've moved forward with Atlassian to help clients streamline project management.
The following is a small sampling of some of the flexibility that we are seeing from this suite of tools:
HotWax Media has reviewed several project management packages. Our aim being to solve project management and work flow difficulties. In collaboration with our managed hosting partner, Contegix, we discovered the Atlassian suite of tools. Contegix gave the stamp of approval and we've moved forward with Atlassian to help clients streamline project management.
The following is a small sampling of some of the flexibility that we are seeing from this suite of tools:
- Protecting access to applications and source code
- Managing documents and documentation
- Showing SVN changesets for performing code review
- Crowd - a centralized single sign on with permissions and access that easily plugs to a variety of applications
- Confluence – powerful document management and collaboration
- FishEye – reporting of source code and repository changes in real time
- Crucible – code and document review
- JIRA – project management and tracking
Friday, June 4, 2010
OFBiz Tutorial - User Permissions
OFBiz Tutorial discussing set-up of user permissions. Apache OFBiz is an open-source enterprise eCommerce project that has collaborators from all over the world. OFBiz tutorials are a valuable resource that many OFBiz developers post for free on the web so that their clients and other users of OFBiz can have the most up-to-date information on how to use the platform as well as the new features that are available.
Apache OFBiz has a base permission for every application sans ecommerce, ofbizwesite and a few others. In order for users to login to the application, they should have "base OFBiz permission view" or "base permission admin". Base permission may consist of more than one permission in which case all permissions are required for a login.
Definition | OFBiz Tutorials
Base permission is defined in the ofbiz-component.xml file for each component. Multiple permissions are separated by a comma character.
Step by Step | OFBiz Tutorials
Now we will set-up permissions for a new user to gain access to a back-end application. We will use an Asset Maint component as an example throughout the tutorial.
First we will create a new user. Login to the party manager app. with the username "admin" and password "ofbiz". Click on the "Create New" link which is located at the top of the main screen.
You will be presented with a variety of options, Choose "Create New Person".
Enter the required fields (name, title, etc.) and save.
Now you will be directed back to the user profile screen.
We will now create a user login. Click "Create New" link on the user name(s) screen in the right column
Enter the following details:
Click on the "Security Group" link. You will be presented with a screen that allows you to add a security group to the user. This will allow you to set the permissions for that user. The permissions are classified as "View", "Create", "Update" and "Delete". An admin security group contains all of these permissions. Select the "Asset Maint Admin" group from the drop-down menu. The field for "From Date" is optional and if no value is entered, the application will use the system's timestamp. "Thru Date" is also optional, this allows you to select a time frame for the permissions if desired. You also have the option to assign multiple security groups to the same user. When done, click "save".
The user now has permission to access the "Asset Maint" application.
Note: The admin user is available only if demo data is installed. If only seed data is installed then you have to create the admin user through the command line with an ant target defined in the build file which is present at the root of the project. Run command create-admin-user-login from the terminal and follow onscreen instructions to complete this wizard.
Testing Permissions | OFBiz Tutorial
You can check for "update" or "delete" permission by updating or deleting the mock fixed asset record you just created.
If you try to log into another application that doesn't have a permission set up under this user they will not have access.
This is an overview of user permissions. As you familiarize yourself with the interface you will be able to take advantage of the various permissions options available.
Enterprise eCommerce makes it very easy for you to update, inventory, manage and maintain your operation with full automation of many processes. OFBiz, once implemented can be easily updated and maintained and integrates with most other platforms that you will use (such as shipping and payment options). Taking advantage of OFBiz tutorials gives you an edge on the competition and streamlines your business. For more information on enterprise eCommerce and Apache OFBiz, contact HotWax Media at 888-405-2667.
Apache OFBiz has a base permission for every application sans ecommerce, ofbizwesite and a few others. In order for users to login to the application, they should have "base OFBiz permission view" or "base permission admin". Base permission may consist of more than one permission in which case all permissions are required for a login.
Definition | OFBiz Tutorials
Base permission is defined in the ofbiz-component.xml file for each component. Multiple permissions are separated by a comma character.
Step by Step | OFBiz Tutorials
Now we will set-up permissions for a new user to gain access to a back-end application. We will use an Asset Maint component as an example throughout the tutorial.
First we will create a new user. Login to the party manager app. with the username "admin" and password "ofbiz". Click on the "Create New" link which is located at the top of the main screen.
You will be presented with a variety of options, Choose "Create New Person".
Enter the required fields (name, title, etc.) and save.
Now you will be directed back to the user profile screen.
We will now create a user login. Click "Create New" link on the user name(s) screen in the right column
Enter the following details:
- User Login ID: joe.will
- Current Password: ofbiz
- Current Password verify: ofbiz
Click on the "Security Group" link. You will be presented with a screen that allows you to add a security group to the user. This will allow you to set the permissions for that user. The permissions are classified as "View", "Create", "Update" and "Delete". An admin security group contains all of these permissions. Select the "Asset Maint Admin" group from the drop-down menu. The field for "From Date" is optional and if no value is entered, the application will use the system's timestamp. "Thru Date" is also optional, this allows you to select a time frame for the permissions if desired. You also have the option to assign multiple security groups to the same user. When done, click "save".
The user now has permission to access the "Asset Maint" application.
Note: The admin user is available only if demo data is installed. If only seed data is installed then you have to create the admin user through the command line with an ant target defined in the build file which is present at the root of the project. Run command create-admin-user-login from the terminal and follow onscreen instructions to complete this wizard.
Testing Permissions | OFBiz Tutorial
Logout of the party manager so you can login to the asset maint app. with the new user. If everything was filled out correctly there should be no problem with the login. Once successfully logged in, the user now has permission to "view" this application.
You can check for "update" or "delete" permission by updating or deleting the mock fixed asset record you just created.
If you try to log into another application that doesn't have a permission set up under this user they will not have access.
This is an overview of user permissions. As you familiarize yourself with the interface you will be able to take advantage of the various permissions options available.
Enterprise eCommerce makes it very easy for you to update, inventory, manage and maintain your operation with full automation of many processes. OFBiz, once implemented can be easily updated and maintained and integrates with most other platforms that you will use (such as shipping and payment options). Taking advantage of OFBiz tutorials gives you an edge on the competition and streamlines your business. For more information on enterprise eCommerce and Apache OFBiz, contact HotWax Media at 888-405-2667.
Subscribe to:
Posts (Atom)
